crow_remove_backend

THE RISK

Critical Risk

Why crow_remove_backend needs a policy

This tool permanently removes a backend registration with no ability to recover or undo the action. While the confirmation token pattern mitigates some risk, the irreversible nature of deletion places this firmly in the Destructive category rather than Write.

From the tool's definition "Remove a data backend registration. This cannot be undone." The description explicitly states the action cannot be undone, which is the defining characteristic of destructive operations.

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

POLICY

How to control crow_remove_backend

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

policy.json

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

crow_remove_backend 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 Crow — 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 Crow tools

Financial crow_tax_prepare_from_documents One-step tax return preparation: creates a return from ALL confirmed documents uploaded th Financial crow_actual_create_transaction Create a new transaction. Amount in cents (negative = expense, positive = income). Financial crow_tax_set_capital_gains Add Schedule D capital gain/loss transactions. Destructive caddy_remove_site Remove a site block from the Caddyfile (matched by address) and reload Caddy. Destructive Destructive crow_bookstack_delete Delete a page or chapter from BookStack (irreversible) Destructive crow_campaign_delete Delete a campaign and all its posts. Requires confirmation. Destructive crow_crosspost_cancel Cancel a queued cross-post before its scheduled_at fires. Idempotent — cancelling an alrea Destructive crow_delete_context_section Delete a custom crow.md section. Protected sections cannot be deleted — only disabled. Sco

All 576 Crow 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 Crow → 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 crow_remove_backend

What does the crow_remove_backend tool do? +

Remove a data backend registration. This cannot be undone. Returns a preview and confirmation token on first call; pass the token back to execute. 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_remove_backend? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_remove_backend: 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_remove_backend? +

crow_remove_backend 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_remove_backend? +

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

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

crow_remove_backend 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.

Enforce policy on every Crow tool call.

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

CHECK YOUR STACK →