Delete multiple relations from the knowledge graph
AI agents call delete_relations to permanently remove resources in Neo4j MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes relationship data from the Neo4j knowledge graph without the ability to undo the operation. Deletion of graph relations is irreversible and constitutes a destructive action. The 'multiple relations' aspect increases blast radius if misused by an agent. While not as severe as deleting all entities, removing relation data can break graph integrity and analysis.
From the tool's definition Tool name 'delete_relations' and description 'Delete multiple relations from the knowledge graph' explicitly indicate irreversible deletion of data.
Attacks that exploit this kind of access
Delete multiple relations from the knowledge graph. It is categorised as a Destructive tool in the Neo4j MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Neo4j MCP Server MCP server in PolicyLayer and add a rule for delete_relations: 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 Neo4j MCP Server. Nothing to install.
delete_relations 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_relations 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_relations. 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_relations is provided by the Neo4j MCP Server MCP server (rebots-online/mcp-neo4j). 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 →