// MCP TOOL REFERENCE

clear_graph

ServerGraphiti Knowledge Graph MCP Server
CategoryDestructive

WHAT IT DOES

What clear_graph does on Graphiti Knowledge Graph MCP Server

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

THE RISK

Critical Risk

Why clear_graph needs a policy

This tool performs irreversible deletion of all data ('clear all data'), which is the definition of Destructive. While it requires password authentication (a mitigating control), the underlying action remains an unrecoverable wipe of the entire knowledge graph. Severity is high because the blast radius affects the entire persistent memory system across all interactions.

From the tool's definition Tool description states: 'Clear all data from the knowledge graph and rebuild indices' — this irreversibly deletes all data in the knowledge graph.

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control clear_graph

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 clear_graph:

policy.json

{
  "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.

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 delete_entity_edge Delete an entity edge from the knowledge graph 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 clear_graph

What does the clear_graph tool do? +

Clear all data from the knowledge graph and rebuild indices. Requires password authentication - the password parameter must match the CLEAR_GRAPH_PASSWORD environment variable. If CLEAR_GRAPH_PASSWORD is not configured on the server, this tool will be disabled and return an error. 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 clear_graph? +

Register the Graphiti Knowledge Graph MCP Server 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 Knowledge Graph MCP Server. Nothing to install.

What risk level is clear_graph? +

clear_graph 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 clear_graph? +

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.

How do I block clear_graph completely? +

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.

What MCP server provides clear_graph? +

clear_graph 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 →

Free to start. No card required.

11 Graphiti Knowledge Graph MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.