Delete an episode from the Graphiti knowledge graph. Args: uuid: UUID of the episode to delete
AI agents call delete_episode 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.
This tool irreversibly deletes data from a Neo4j database. Deletion of episodes cannot be undone and represents permanent data loss. While the blast radius is bounded to a single episode rather than the entire graph, the destructive nature of the operation and the high value of knowledge graph data warrant a 'high' severity rating.
From the tool's definition Tool name is 'delete_episode' and description states 'Delete an episode from the Graphiti knowledge graph.' The use of 'Delete' and the action of removing an episode from a persisted Neo4j knowledge graph indicates irreversible data removal.
Documented attack patterns abuse exactly the kind of access delete_episode gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Graphiti MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_episode:
{
"version": "1",
"default": "deny",
"hide": [
"delete_episode"
]
}delete_episode disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an episode from the Graphiti knowledge graph. Args: uuid: UUID of the episode to delete. 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_episode: 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_episode 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_episode 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_episode. 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_episode is provided by the Graphiti MCP Server MCP server (rawr-ai/mcp-graphiti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Graphiti MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Graphiti MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.