Rebuild the local typed graph side index from Obsidian memories.
AI agents call memory_graph_rebuild to retrieve information from Cortex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though memory_graph_rebuild only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Documented attack patterns abuse exactly the kind of access memory_graph_rebuild gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cortex, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_graph_rebuild:
{
"version": "1",
"default": "deny",
"tools": {
"memory_graph_rebuild": {}
}
}memory_graph_rebuild 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.
Rebuild the local typed graph side index from Obsidian memories. It is categorised as a Read tool in the Cortex MCP Server, which means it retrieves data without modifying state.
Register the Cortex MCP server in PolicyLayer and add a rule for memory_graph_rebuild: 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 Cortex. Nothing to install.
memory_graph_rebuild 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_rebuild 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_rebuild. 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_rebuild is provided by the Cortex MCP server (tt-wang/memem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Cortex tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Cortex tools catalogued and risk-classified — across an index of 42,500+ MCP servers.