AI agents call pulse_get_info to retrieve information from Pulse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static system metadata (directory path, version number) about the Pulse application itself. It performs a query operation with no capability to modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only learn harmless information about the system's Pulse installation.
From the tool's definition Tool name 'pulse_get_info' and description 'Get system information (directory, version)' indicate retrieval of data with no side effects. The verbs 'get' and 'information retrieval' are characteristic of Read operations.
Attacks that exploit this kind of access
Get system information (directory, version). It is categorised as a Read tool in the Pulse MCP Server, which means it retrieves data without modifying state.
Register the Pulse MCP server in PolicyLayer and add a rule for pulse_get_info: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Pulse. Nothing to install.
pulse_get_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pulse_get_info rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for pulse_get_info. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
pulse_get_info is provided by the Pulse MCP server (nemesiscodex/pulse-tm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →