memory_link · Exocortex MCP: Risk & Policy

WHAT IT DOES

What memory_link does on Exocortex

AI agents use memory_link to create or update resources in Exocortex — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Exocortex environment.

WHY IT NEEDS A POLICY

Why memory_link needs a policy

The tool writes graph edges (links) between memory entries. Creating a link is a reversible write operation. Removing a link is also covered ('or remove'), which could be considered mildly destructive, but since links can be recreated, it remains reversible. The most severe applicable category is Write. Misuse could corrupt memory graph topology, affecting retrieval quality for the AI agent, hence medium severity.

From the tool's definition 'Create or remove a link between two memories' — creates or modifies relationships between existing memory nodes

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_link Rate-limited

memory_link stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_link": {
      "limits": [
        {
          "counter": "memory_link_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_link

What does the memory_link tool do? +

Create or remove a link between two memories. Links enable graph-aware context retrieval — linked memories surface together during context loading. It is categorised as a Write tool in the Exocortex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_link? +

Register the Exocortex MCP server in PolicyLayer and add a rule for memory_link: 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_link? +

memory_link is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memory_link? +

Yes. Add a rate_limit block to the memory_link 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_link completely? +

Set action: deny in the PolicyLayer policy for memory_link. 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_link? +

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