Clear all data from the graph for specified group IDs.
AI agents call clear_graph to permanently remove resources in local-RAG-backend — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data without reversibility or undo capability. The ability to clear 'all data from the graph' for specified groups represents a complete data loss operation affecting the core knowledge store of the RAG system. The blast radius is critical as an AI agent with access could wipe entire knowledge bases, relationships, and indexed documents.
From the tool's definition Tool name 'clear_graph' combined with description 'Clear all data from the graph for specified group IDs' indicates irreversible deletion of potentially large datasets stored in the Neo4j graph backend.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all data from the graph for specified group IDs. It is categorised as a Destructive tool in the local-RAG-backend MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the local-RAG-backend 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 local-RAG-backend. 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 local-RAG-backend MCP server (suwa-sh/local-rag-backend). 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 →