crow_remove_backend

Remove a data backend registration. This cannot be undone. Returns a preview and confirmation token on first call; pass the token back to execute.

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-remove-backend.md

WHAT IT DOES

What crow_remove_backend does on Crow

AI agents call crow_remove_backend 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.

RISK

Why crow_remove_backend is rated Critical

The tool performs an irreversible deletion of a backend registration. Even though it implements a confirmation step (preview + token), the underlying action is destructive and cannot be undone. This matches the Destructive category definition.

From the tool's definition Tool description explicitly states "This cannot be undone" and removes a data backend registration, which irreversibly deletes or overwrites system configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crow_remove_backend safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_remove_backend, this is the rule to start with:

crow_remove_backend Hidden

crow_remove_backend is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_remove_backend call is checked against it from then on.

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.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →