delete_entities

Delete multiple entities from the knowledge graph

SERVEREnhanced Knowledge Graph Memory Server SOURCEdanielsimonjr/memory-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_entities

What does the delete_entities tool do? +

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.

How do I enforce a policy on delete_entities? +

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.

What risk level is delete_entities? +

delete_entities is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_entities? +

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.

How do I block delete_entities completely? +

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.

What MCP server provides delete_entities? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Enhanced Knowledge Graph Memory Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.