memory_compile · Exocortex MCP: Risk & Policy

WHAT IT DOES

What memory_compile does on Exocortex

AI agents invoke memory_compile to trigger actions in Exocortex. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why memory_compile needs a policy

This tool executes a procedural operation to reorganize and process stored memory data rather than simply reading or writing individual entries. While not destructive or financial, the compilation process is an active computational task that could consume resources, modify the state of a cache or output directory, or have side effects depending on how the compiler is invoked.

From the tool's definition The tool 'compile' performs a non-trivial computational operation ('compile the memory system into a browsable wiki') that transforms and structures stored data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_compile Rate-limited

memory_compile stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_compile": {
      "limits": [
        {
          "counter": "memory_compile_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Exocortex, so you can run agents against it safely.

FAQ

Questions about memory_compile

What does the memory_compile tool do? +

Compile the memory system into a browsable wiki of interlinked markdown articles. It is categorised as a Execute tool in the Exocortex MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on memory_compile? +

Register the Exocortex MCP server in PolicyLayer and add a rule for memory_compile: 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.

What risk level is memory_compile? +

memory_compile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit memory_compile? +

Yes. Add a rate_limit block to the memory_compile 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.

How do I block memory_compile completely? +

Set action: deny in the PolicyLayer policy for memory_compile. 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.

What MCP server provides memory_compile? +

memory_compile 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.