delete_connection

THE RISK

Critical Risk

Why delete_connection needs a policy

This tool permanently removes semantic relationships (edges) between memory nodes. While not as severe as deleting entire memories, deletion of connections is irreversible and could break important contextual links that an AI agent relies on for reasoning and decision-making. An AI agent could maliciously or erroneously sever critical knowledge connections, degrading memory integrity.

From the tool's definition Tool name 'delete_connection' and description 'Delete a specific connection between two memories' explicitly perform irreversible deletion of graph relationships in the Neo4j memory store.

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

POLICY

How to control delete_connection

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

policy.json

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

delete_connection 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 Neo4j Agent Memory MCP Server — 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 Neo4j Agent Memory MCP Server tools

Destructive delete_memory Delete a memory and all its connections Write create_connection Create a connection between two memories (it Write create_memory Create a new memory in the knowledge graph (remember to connect it to related memories). C Write update_connection Update properties of an existing connection between memories Write update_memory Update properties of an existing memory Read get_guidance Get help on using the memory tools effectively Read list_memory_labels List all unique memory labels currently in use with their counts Read search_memories Search and retrieve memories from the knowledge graph

All 9 Neo4j Agent Memory MCP Server 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 Neo4j Agent Memory MCP Server → 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_connection

What does the delete_connection tool do? +

Delete a specific connection between two memories. It is categorised as a Destructive tool in the Neo4j Agent Memory MCP 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_connection? +

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

What risk level is delete_connection? +

delete_connection 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_connection? +

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

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

delete_connection is provided by the Neo4j Agent Memory MCP Server MCP server (knowall-ai/mcp-neo4j-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Neo4j Agent Memory MCP Server tool call.

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

CHECK YOUR STACK →