Critical Risk →

delete_relations

Delete multiple relations from the knowledge graph

How to control delete_relations ↓

AI agents call delete_relations to permanently remove resources in Knowledge Graph Memory Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool irreversibly removes data structures (relations) from a persistent knowledge graph. Even though it's scoped to relations rather than entire entities, deletion of relations breaks connections in the graph and cannot be undone, making this a Destructive operation rather than Write.

From the tool's definition Tool name 'delete_relations' and description 'Delete multiple relations from the knowledge graph' explicitly indicate irreversible deletion of data.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Knowledge Graph Memory Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_relations:

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

delete_relations 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 Knowledge Graph Memory Server — 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.

Go deeper

What does the delete_relations tool do? +

Delete multiple relations from the knowledge graph. It is categorised as a Destructive tool in the Knowledge Graph Memory Server 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 delete_relations? +

Register the Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for delete_relations: 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 Knowledge Graph Memory Server. Nothing to install.

What risk level is delete_relations? +

delete_relations 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 delete_relations? +

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

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

delete_relations is provided by the Knowledge Graph Memory Server MCP server (t1nker-1220/memories-with-lessons-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 Knowledge Graph Memory Server tool call.

Deterministic rules across all 13 Knowledge Graph Memory Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

13 Knowledge Graph Memory Server tools catalogued and risk-classified — across an index of 42,500+ 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.