Delete multiple entities and their associated relations from the knowledge graph
AI agents call delete_entities to permanently remove resources in Knowledge Graph Memory Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data from the knowledge graph, including entities and their associated relations. Deletion cannot be undone and represents a destructive operation. While the blast radius may be limited to knowledge graph data (not production systems or financial data), the high confidence in destructive intent and the permanent nature of the action justify 'high' severity.
From the tool's definition Tool name 'delete_entities' and description 'Delete multiple entities and their associated relations from the knowledge graph' explicitly indicate permanent removal of data.
Documented attack patterns abuse exactly the kind of access delete_entities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Knowledge Graph Memory Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_entities:
{
"version": "1",
"default": "deny",
"hide": [
"delete_entities"
]
}delete_entities disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete multiple entities and their associated relations from the knowledge graph. It is categorised as a Destructive tool in the Knowledge Graph Memory Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 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 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 Knowledge Graph Memory Server MCP server (yodakeisuke/mcp-memory-domain-knowledge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Knowledge Graph Memory Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Knowledge Graph Memory Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.