AI agents call read_graph to retrieve information from Mnemex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming pattern 'read_' combined with 'graph' in a memory management context indicates data retrieval without modification. No side effects are apparent from the tool name or server functionality. The empty description prevents higher confidence, but the context of sibling tools (query-like: open_memories, get_performance_metrics, observe_memory_usage) supports a Read classification.
From the tool's definition Tool name 'read_graph' and context of a memory management system suggest querying/retrieving graph structure data. Description is empty, limiting certainty.
Documented attack patterns abuse exactly the kind of access read_graph gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mnemex, and nothing reaches the server without passing your rules. This is the rule we recommend for read_graph:
{
"version": "1",
"default": "deny",
"tools": {
"read_graph": {}
}
}read_graph is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
read_graph. It is categorised as a Read tool in the Mnemex MCP Server, which means it retrieves data without modifying state.
Register the Mnemex MCP server in PolicyLayer and add a rule for read_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 Mnemex. Nothing to install.
read_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 read_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 read_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.
read_graph is provided by the Mnemex MCP server (prefrontal-systems/cortexgraph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Mnemex tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Mnemex tools catalogued and risk-classified — across an index of 42,500+ MCP servers.