AI agents call agloop_get_compaction_context to retrieve information from Agloop without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves diagnostic and recovery information about the compaction state of the AgLoop agent framework. It performs a read-only query operation with no side effects, no data modification, and no external execution. The context it returns is used for monitoring and recovery purposes, not for performing actions.
From the tool's definition Tool name contains 'get_' prefix and description states it retrieves context information (compaction count, pending decision, last delegation, recovery hint) with no mention of modification, deletion, or execution of operations.
Attacks that exploit this kind of access
Get compaction recovery context: compaction count, pending decision, last delegation, recovery hint. Critical after VS Code context compaction. It is categorised as a Read tool in the Agloop MCP Server, which means it retrieves data without modifying state.
Register the Agloop MCP server in PolicyLayer and add a rule for agloop_get_compaction_context: 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 Agloop. Nothing to install.
agloop_get_compaction_context 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 agloop_get_compaction_context 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 agloop_get_compaction_context. 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.
agloop_get_compaction_context is provided by the Agloop MCP server (zebbern/agloop-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 →