Delete multiple entities and their associated relations from the knowledge graph
AI agents call mcp_memory_delete_entities to permanently remove resources in MCP Memory Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly removes data (entities and relations) from persistent storage. Once deleted, the knowledge graph state cannot be recovered unless backups exist. This is a destructive operation with high blast radius if an AI agent mistakenly deletes critical memories or knowledge entities.
From the tool's definition Tool name contains 'delete' and description states 'Delete multiple entities and their associated relations from the knowledge graph' — this is irreversible deletion of data.
Attacks that exploit this kind of access
Delete multiple entities and their associated relations from the knowledge graph. It is categorised as a Destructive tool in the MCP Memory Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Memory Server MCP server in PolicyLayer and add a rule for mcp_memory_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 MCP Memory Server. Nothing to install.
mcp_memory_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 mcp_memory_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 mcp_memory_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.
mcp_memory_delete_entities is provided by the MCP Memory Server MCP server (jessefreitas/mcp_memory). 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 →