AI agents call spreader_status to retrieve information from Cartridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistics about system loops and token usage. It performs a read operation that queries current state without modifying, executing code, or destructive actions. The blast radius of misuse is minimal—an agent can only view metrics that should typically be observable. Severity is low as this provides operational visibility only.
From the tool's definition 'Get current loop statistics — iterations, tokens, success rate' is a query operation that retrieves monitoring/diagnostic data with no side effects.
Attacks that exploit this kind of access
Get current loop statistics — iterations, tokens, success rate. It is categorised as a Read tool in the Cartridge MCP Server, which means it retrieves data without modifying state.
Register the Cartridge MCP server in PolicyLayer and add a rule for spreader_status: 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 Cartridge. Nothing to install.
spreader_status 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 spreader_status 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 spreader_status. 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.
spreader_status is provided by the Cartridge MCP server (lucineer/cartridge-mcp). 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 →