crow_linkding_delete

Delete a bookmark from Linkding. This is permanent.

SERVERCrow SOURCEkh0pper/crow
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/kh0pper-crow/crow-linkding-delete.md

What crow_linkding_delete does on Crow

AI agents call crow_linkding_delete to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why crow_linkding_delete is rated Critical

This tool permanently deletes data (bookmarks) from an external service with no ability to recover or reverse the action. Destructive operations are those that irreversibly remove or destroy data. An AI agent misusing this tool could permanently lose user bookmarks with no recovery path, affecting project management workflows that depend on saved references.

From the tool's definition Tool description explicitly states "Delete a bookmark from Linkding. This is permanent." The words "Delete" and "permanent" clearly indicate an irreversible action that cannot be undone.

Questions about crow_linkding_delete

What does the crow_linkding_delete tool do? +

Delete a bookmark from Linkding. This is permanent. It is categorised as a Destructive tool in the Crow 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 crow_linkding_delete? +

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

What risk level is crow_linkding_delete? +

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

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

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

crow_linkding_delete is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Crow, 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 Crow'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.