delete_relation

THE RISK

Critical Risk

Why delete_relation needs a policy

This tool permanently removes relational data from the memory system. Deletion of relations cannot be undone without manual restoration, making it a destructive action. While the blast radius is somewhat limited compared to deleting entire entities (delete_entity), it still irreversibly modifies the knowledge graph structure. Confidence is high due to explicit use of 'Delete' in both name and description.

From the tool's definition Tool name is 'delete_relation' and description states 'Delete a specific relation between entities'. The verb 'Delete' combined with the irreversible nature of removing relationships in a knowledge graph indicates destructive capability.

Documented attack patterns abuse exactly the kind of access delete_relation gives an agent:

POLICY

How to control delete_relation

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Memory LibSQL, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_relation:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_relation"
  ]
}

delete_relation disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register MCP Memory LibSQL — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Memory LibSQL tools

Destructive delete_entity Delete an entity and all its associated data (observations and relations) Write create_entities Create new entities with observations and optional embeddings Write create_relations Create relations between entities Read read_graph Get recent entities and their relations Read search_nodes Search for entities and their relations using text or vector similarity

All 6 MCP Memory LibSQL tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MCP Memory LibSQL → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_relation

What does the delete_relation tool do? +

Delete a specific relation between entities. It is categorised as a Destructive tool in the MCP Memory LibSQL 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_relation? +

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

What risk level is delete_relation? +

delete_relation 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_relation? +

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

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

delete_relation is provided by the MCP Memory LibSQL MCP server (joleyline/mcp-memory-libsql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Memory LibSQL tool call.

Start from MCP Memory LibSQL, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →