delete_entity_edge

THE RISK

Critical Risk

Why delete_entity_edge needs a policy

The tool permanently removes relationships (edges) between entities in the knowledge graph. This is an irreversible destructive operation that cannot be undone without manual restoration. While the blast radius is somewhat contained (only affects graph edges, not core data), the permanent nature of deletion and potential loss of important relationship information justifies 'Destructive' classification over 'Write'.

From the tool's definition Tool name explicitly uses 'delete' and description states 'Delete an entity edge from the knowledge graph'. The action removes data from the knowledge graph irreversibly.

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

POLICY

How to control delete_entity_edge

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_entity_edge"
  ]
}

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

Create a free account and register Graphiti Knowledge Graph MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Graphiti Knowledge Graph MCP Server tools

Destructive clear_graph Clear all data from the knowledge graph and rebuild indices. Requires password authenticat Destructive delete_episode Delete an episode from the knowledge graph Destructive delete_everything_by_group_id Delete all data (episodes, nodes, and entity edges) associated with a group_id. This is an Write add_episode Add an episode to the knowledge graph (supports text, JSON, and message formats) Read get_entity_edge Get an entity edge by its UUID Read get_episodes Get the most recent episodes for a specific group Read get_queue_status Get the current status of all episode processing queues. Shows total pending tasks, active Read get_status Get the status of the Graphiti MCP server and Neo4j connection

All 11 Graphiti Knowledge Graph MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Graphiti Knowledge Graph MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_entity_edge

What does the delete_entity_edge tool do? +

Delete an entity edge from the knowledge graph. It is categorised as a Destructive tool in the Graphiti Knowledge Graph MCP 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_entity_edge? +

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

What risk level is delete_entity_edge? +

delete_entity_edge 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_entity_edge? +

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

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

delete_entity_edge is provided by the Graphiti Knowledge Graph MCP Server MCP server (michabbb/graphiti-mcp-but-working). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Graphiti Knowledge Graph MCP Server tool call.

Start from Graphiti Knowledge Graph MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →