AI agents call get_usage to retrieve information from Pulspeed without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries usage data without creating, modifying, deleting, executing code, or committing financial transactions. It is a straightforward read operation that returns account/usage metrics. The blast radius of misuse is minimal—an agent could only learn usage patterns or quota information, which has no material impact.
From the tool's definition Tool description states it 'Get[s] current API usage statistics' - a retrieval operation with no mutations or side effects. The metrics retrieved (scans used, quota, plan limits) are informational only.
Attacks that exploit this kind of access
Get current API usage statistics: how many scans and AI analyses have been used this month, remaining quota, and plan limits. It is categorised as a Read tool in the Pulspeed MCP Server, which means it retrieves data without modifying state.
Register the Pulspeed MCP server in PolicyLayer and add a rule for get_usage: 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 Pulspeed. Nothing to install.
get_usage 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 get_usage 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 get_usage. 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.
get_usage is provided by the Pulspeed MCP server (pulspeed/mcp-server). 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 →