Critical Risk →

crow_bookstack_delete

Delete a page or chapter from BookStack (irreversible)

How to control crow_bookstack_delete ↓

What crow_bookstack_delete does on Crow

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

Critical Risk

Why crow_bookstack_delete needs a policy

This tool permanently removes data from BookStack without possibility of recovery. The irreversible nature and potential to delete entire chapters of documentation makes it a destructive action with high blast radius if misused by an AI agent. Classified as Destructive rather than Write because deletion cannot be undone.

From the tool's definition Tool name includes 'delete' and description explicitly states 'Delete a page or chapter from BookStack (irreversible)' — the word 'irreversible' confirms destructive intent.

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

How to control crow_bookstack_delete

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_bookstack_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "crow_bookstack_delete"
  ]
}

crow_bookstack_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about crow_bookstack_delete

What does the crow_bookstack_delete tool do? +

Delete a page or chapter from BookStack (irreversible). 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_bookstack_delete? +

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

crow_bookstack_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_bookstack_delete? +

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

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

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

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.

Free to start. No card required.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.