Critical Risk →

delete_entity_edge

Delete an entity edge from the graph memory.

How to control delete_entity_edge ↓

What delete_entity_edge does on Graphiti MCP Demo

AI agents call delete_entity_edge to permanently remove resources in Graphiti MCP Demo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_entity_edge needs a policy

This tool performs an irreversible deletion operation on persisted graph data. Once an entity edge is deleted from the knowledge graph, the relationship is permanently removed and cannot be undone through normal use.

From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete an entity edge from the graph memory.' The action irreversibly removes a relationship between entities in a Neo4j-backed knowledge graph.

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

How to control delete_entity_edge

PolicyLayer is an MCP gateway — it sits between your AI agents and Graphiti MCP Demo, 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.

  1. Create a free account and register Graphiti MCP Demo — 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 delete_entity_edge

What does the delete_entity_edge tool do? +

Delete an entity edge from the graph memory. It is categorised as a Destructive tool in the Graphiti MCP Demo 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 MCP Demo 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 MCP Demo. 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 MCP Demo MCP server (kartikk-26/graphiti-mcp-demo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Graphiti MCP Demo tool call.

Start from Graphiti MCP Demo, 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.

8 Graphiti MCP Demo 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.