New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_relations

Delete multiple relations

SERVERMCP Memory Server with Qdrant Persistence SOURCEdelorenj/mcp-qdrant-memory
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/delorenj-mcp-qdrant-memory/delete-relations.md

What delete_relations does on MCP Memory Server with Qdrant Persistence

AI agents call delete_relations 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_relations is rated Critical

This tool permanently removes relations from the knowledge graph without the ability to undo the action (no mention of soft-delete, archive, or rollback). Deletion of multiple relations at once increases the blast radius.

From the tool's definition Tool name is 'delete_relations' and description states 'Delete multiple relations'. The verb 'delete' combined with 'multiple' indicates irreversible removal of data from the knowledge graph.

Questions about delete_relations

What does the delete_relations tool do? +

Delete multiple 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.

How do I enforce a policy on delete_relations? +

Register the MCP Memory Server with Qdrant Persistence MCP server in PolicyLayer and add a rule for delete_relations: 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.

What risk level is delete_relations? +

delete_relations 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_relations? +

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

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

delete_relations 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.

// 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 MCP Memory Server with Qdrant Persistence'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.