delete_entities

Delete multiple entities and their associated relations from the knowledge graph

Server MCP Memory Server stevenwangler/mcp-memory-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_entities does on MCP Memory Server

AI agents call 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.

Why delete_entities needs a policy

This tool permanently removes entities and all associated relations from the knowledge graph. Deletion is irreversible and affects interconnected data (relations). While the blast radius is limited to the specific knowledge graph (not financial or system-critical), misuse by an AI agent could destroy important stored knowledge, reasoning artifacts, or conversation history that cannot be recovered.

From the tool's definition Tool name is 'delete_entities' and description states 'Delete multiple entities and their associated relations from the knowledge graph' — irreversible deletion of data with cascading effects on related records.

Questions about delete_entities

What does the delete_entities tool do? +

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.

How do I enforce a policy on delete_entities? +

Register the MCP 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 MCP 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 MCP Memory Server MCP server (stevenwangler/mcp-memory-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.