AI agents call memory_get to retrieve information from Exocortex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored memory data by ID without creating, modifying, or deleting content. It is a pure read operation consistent with query/fetch functions. The usefulness ranking is an informational side effect, not a destructive or financial action. Low severity because the blast radius is limited to information disclosure of locally-stored memories without broader system impact.
From the tool's definition Tool description states 'Fetch full content for specific memory IDs' — a retrieval operation with no modification or deletion capability. The phrase 'Implicitly signals usefulness for future ranking' indicates metadata tagging rather than destructive action.
Attacks that exploit this kind of access
Fetch full content for specific memory IDs. Implicitly signals usefulness for future ranking. It is categorised as a Read tool in the Exocortex MCP Server, which means it retrieves data without modifying state.
Register the Exocortex MCP server in PolicyLayer and add a rule for memory_get: 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 Exocortex. Nothing to install.
memory_get 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 memory_get 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 memory_get. 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.
memory_get is provided by the Exocortex MCP server (shawnhack/exocortex). 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 →