zk_remove_link

THE RISK

Critical Risk

Why zk_remove_link needs a policy

Removing a link between notes is an irreversible deletion of a relationship/connection in the knowledge graph. Unlike editing note content, link removal destroys the association between notes without an implied undo mechanism, making it Destructive. Severity is medium as it affects knowledge structure/navigation but doesn't delete the notes themselves.

From the tool's definition Remove an existing link between two notes

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

POLICY

How to control zk_remove_link

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

policy.json

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

zk_remove_link 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 Zettelkasten — 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 Zettelkasten tools

Destructive zk_delete_note Permanently delete a note and all its associated links from the Zettelkasten. Execute zk_rebuild_index Rebuild the database index from markdown files after manual file edits. Write zk_create_link Create a semantic link between two notes to build knowledge connections. Write zk_create_note Create a new atomic Zettelkasten note with a unique ID, content, and optional tags. Write zk_update_note Update the title, content, type, or tags of an existing note. Read zk_find_central_notes Identify the most connected notes that serve as knowledge hubs. Read zk_find_orphaned_notes Find isolated notes that have no links to or from other notes. Read zk_find_similar_notes Discover notes with similar content using semantic similarity analysis.

All 14 Zettelkasten 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 Zettelkasten → 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 zk_remove_link

What does the zk_remove_link tool do? +

Remove an existing link between two notes. It is categorised as a Destructive tool in the Zettelkasten 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 zk_remove_link? +

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

What risk level is zk_remove_link? +

zk_remove_link 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 zk_remove_link? +

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

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

zk_remove_link is provided by the Zettelkasten MCP server (liam-deacon/zettelkasten-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Zettelkasten tool call.

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

CHECK YOUR STACK →