delete_entities
AI agents call delete_entities to permanently remove resources in Neo4j Knowledge Graph — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of entities from a knowledge graph is irreversible and represents permanent data loss. Even though the tool description is empty, the name combined with the server description clearly indicates this removes data without possibility of recovery. This qualifies as Destructive rather than just Write.
From the tool's definition Tool name is 'delete_entities' which explicitly indicates irreversible deletion of data. Combined with the server's stated capability to 'delete entities...in a Neo4j-powered knowledge graph', this is a destructive operation that cannot be undone.
Attacks that exploit this kind of access
delete_entities. It is categorised as a Destructive tool in the Neo4j Knowledge Graph MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Neo4j Knowledge Graph MCP server in PolicyLayer and add a rule for delete_entities: 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 Knowledge Graph. Nothing to install.
delete_entities 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_entities 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_entities. 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_entities is provided by the Neo4j Knowledge Graph MCP server (mjftw/mcp_neo4j_knowledge_graph). 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 →