Critical Risk →

remove_relation

Removes a relation between two notes.

How to control remove_relation ↓

What remove_relation does on A-MEM: Agentic Memory System

AI agents call remove_relation to permanently remove resources in A-MEM: Agentic Memory System — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why remove_relation needs a policy

Removing a relation between notes deletes a graph edge permanently. There is no indication of a soft-delete or undo mechanism. In a graph-based memory system, relations encode semantic connections that may be difficult or impossible to reconstruct, making this a destructive operation.

From the tool's definition 'Removes a relation between two notes' — the word 'removes' indicates an irreversible deletion of a relationship link in the knowledge graph.

Documented attack patterns abuse exactly the kind of access remove_relation gives an agent:

How to control remove_relation

PolicyLayer is an MCP gateway — it sits between your AI agents and A-MEM: Agentic Memory System, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_relation:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_relation"
  ]
}

remove_relation disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register A-MEM: Agentic Memory System — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about remove_relation

What does the remove_relation tool do? +

Removes a relation between two notes. It is categorised as a Destructive tool in the A-MEM: Agentic Memory System MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_relation? +

Register the A-MEM: Agentic Memory System MCP server in PolicyLayer and add a rule for remove_relation: 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 A-MEM: Agentic Memory System. Nothing to install.

What risk level is remove_relation? +

remove_relation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_relation? +

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

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

remove_relation is provided by the A-MEM: Agentic Memory System MCP server (tobs-code/a-mem-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every A-MEM: Agentic Memory System tool call.

Start from A-MEM: Agentic Memory System, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

15 A-MEM: Agentic Memory System tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.