delete_entities
Delete multiple entities from the knowledge graph
This record as markdown: /tools/danielsimonjr-memory-mcp/delete-entities.md
What delete_entities does on Enhanced Knowledge Graph Memory Server
AI agents call delete_entities to permanently remove resources in Enhanced Knowledge Graph Memory Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_entities is rated Critical
This tool permanently removes entities from persistent storage without apparent undo/recovery mechanism. Deletion is irreversible and affects the knowledge graph's integrity. The ability to delete 'multiple' entities amplifies the blast radius. While not financial, this is more severe than Write (which is reversible) and qualifies as Destructive.
From the tool's definition Tool name 'delete_entities' combined with description 'Delete multiple entities from the knowledge graph' explicitly performs irreversible deletion of data records.
Attacks that exploit this kind of access
The rule that runs delete_entities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_entities, this is the rule to start with:
delete_entities is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every delete_entities call is checked against it from then on.
Questions about delete_entities
Delete multiple entities from the knowledge graph. It is categorised as a Destructive tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Enhanced Knowledge Graph Memory Server 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 Enhanced Knowledge Graph Memory Server. 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 Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
This server
Across the catalogue