delete_entity

A destructive tool on the Optimized Memory MCP Server V2 MCP server.

SERVEROptimized Memory MCP Server V2 SOURCEagentwong/optimized-memory-mcp-serverv2
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/agentwong-optimized-memory-mcp-serverv2/delete-entity.md

What delete_entity does on Optimized Memory MCP Server V2

AI agents call delete_entity to permanently remove resources in Optimized Memory MCP Server V2, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_entity is rated Critical

Deletion operations that cannot be undone fall into the Destructive category. While the description is empty (lowering confidence slightly), the explicit 'delete_' prefix combined with the entity-based data model of this MCP server indicates this tool irreversibly removes stored entities. The blast radius is high if an agent mistakenly deletes critical entities in the memory system.

From the tool's definition Tool name is 'delete_entity' which directly indicates deletion/removal of data. No description provided to clarify scope or reversibility, but 'delete' combined with the pattern of sibling tools (create_entity, create_observation, create_relationship,…

Questions about delete_entity

What does the delete_entity tool do? +

delete_entity is a destructive tool on the Optimized Memory MCP Server V2 MCP server. It is categorised as a Destructive tool in the Optimized Memory MCP Server V2 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_entity? +

Register the Optimized Memory MCP Server V2 MCP server in PolicyLayer and add a rule for delete_entity: 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 Optimized Memory MCP Server V2. Nothing to install.

What risk level is delete_entity? +

delete_entity 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_entity? +

Yes. Add a rate_limit block to the delete_entity 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_entity completely? +

Set action: deny in the PolicyLayer policy for delete_entity. 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_entity? +

delete_entity is provided by the Optimized Memory MCP Server V2 MCP server (agentwong/optimized-memory-mcp-serverv2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Optimized Memory MCP Server V2, 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 Optimized Memory MCP Server V2'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.