# delete_relations

Delete multiple relations

Agent View of the PolicyLayer registry record for `delete_relations`. HTML page: https://policylayer.com/tools/delorenj-mcp-qdrant-memory/delete-relations

## Facts

- Tool: `delete_relations`
- Server: MCP Memory Server with Qdrant Persistence (`delorenj/mcp-qdrant-memory`) — https://policylayer.com/tools/delorenj-mcp-qdrant-memory.md
- Homepage: https://github.com/delorenj/mcp-qdrant-memory
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_relations",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MCP Memory Server with Qdrant Persistence:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_relations"
  ]
}
```

## Other tools on MCP Memory Server with Qdrant Persistence (7)

- `delete_entities` — Destructive — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/delete-entities.md
- `delete_observations` — Destructive — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/delete-observations.md
- `read_graph` — Read — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/read-graph.md
- `search_similar` — Read — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/search-similar.md
- `add_observations` — Write — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/add-observations.md
- `create_entities` — Write — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/create-entities.md
- `create_relations` — Write — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/create-relations.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=delorenj-mcp-qdrant-memory · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/delorenj-mcp-qdrant-memory