Delete an entity edge from the graph memory.
AI agents call delete_entity_edge to permanently remove resources in Graphiti MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs irreversible deletion of data (entity edges) from the knowledge graph. Even though individual edge deletions may have limited scope compared to bulk operations, deletion is inherently destructive and unrecoverable. This exceeds Write (reversible modifications) and maps clearly to the Destructive category.
From the tool's definition Tool name explicitly includes 'delete' and description states it will 'Delete an entity edge from the graph memory.' Deletion of graph edges is an irreversible operation that cannot be undone without reconstruction.
Attacks that exploit this kind of access
Delete an entity edge from the graph memory. It is categorised as a Destructive tool in the Graphiti MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Graphiti 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 MCP Server. Nothing to install.
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.
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.
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.
delete_entity_edge is provided by the Graphiti MCP Server MCP server (tesfandiari1/graphiti-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →