AI agents call memory_graph 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 and analyzes graph structure and relationships to compute centrality metrics and identify knowledge domain connections. These are read-only analytical operations that examine data without modifying, deleting, or executing external operations. No side effects or irreversible actions are possible.
From the tool's definition Tool performs analysis and metrics computation on an existing entity relationship graph: 'Analyze the entity relationship graph — centrality metrics, bridge entities, knowledge domain connections.' The verbs are analytical (analyze, compute metrics) with no…
Attacks that exploit this kind of access
Analyze the entity relationship graph — centrality metrics, bridge entities, knowledge domain connections. 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_graph: 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_graph 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_graph 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_graph. 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_graph 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 →