delete_entities
Delete multiple entities and their relations
This record as markdown: /tools/delorenj-mcp-qdrant-memory/delete-entities.md
What delete_entities does on MCP Memory Server with Qdrant Persistence
AI agents call delete_entities to permanently remove resources in MCP Memory Server with Qdrant Persistence, 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
Deletion of entities and their relations is a destructive operation that cannot be undone. Once deleted, the data and its semantic connections are permanently removed from the graph. The ability to delete 'multiple' entities amplifies the blast radius. This is more severe than Write operations and falls clearly into the Destructive category.
From the tool's definition Tool name 'delete_entities' with description 'Delete multiple entities and their relations' explicitly indicates irreversible deletion of data records and their associated relationships in the knowledge graph.
Attacks that exploit this kind of access
The rule that runs delete_entities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Memory Server with Qdrant Persistence, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_entities, this is the rule to start with:
delete_entities is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Memory Server with Qdrant Persistence, apply this rule, and every delete_entities call is checked against it from then on.
Questions about delete_entities
Delete multiple entities and their relations. It is categorised as a Destructive tool in the MCP Memory Server with Qdrant Persistence MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Memory Server with Qdrant Persistence 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 with Qdrant Persistence. 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 MCP Memory Server with Qdrant Persistence MCP server (delorenj/mcp-qdrant-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Memory Server with Qdrant Persistence, and thousands of servers like it.
This server
Across the catalogue