Clear all data from the graph memory and rebuild indices.
AI agents call clear_graph 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.
This tool performs irreversible deletion of entire datasets (all graph memory), which cannot be undone without restore from backup. It far exceeds Write in scope and severity. The blast radius is high: an AI agent invoking this would wipe the entire knowledge graph context, rendering all prior memory and relationships permanently lost.
From the tool's definition Tool description states 'Clear all data from the graph memory' — explicitly irreversible deletion of all persisted knowledge graph data in Neo4j.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access clear_graph gives an agent:
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 clear_graph:
{
"version": "1",
"default": "deny",
"hide": [
"clear_graph"
]
}clear_graph 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.
Clear all data from the graph memory and rebuild indices. 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.
Register the Graphiti MCP Demo MCP server in PolicyLayer and add a rule for clear_graph: 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.
clear_graph 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 clear_graph 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 clear_graph. 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.
clear_graph 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.
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.