delete_book
Delete a book from BookStack.
This record as markdown: /tools/derron-knox-bookstack-mcp-server/delete-book.md
What delete_book does on BookStack MCP Server
AI agents call delete_book to permanently remove resources in BookStack MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_book is rated Critical
Deleting a book is irreversible and removes data that cannot be easily recovered without backups. This action has significant blast radius if triggered unintentionally by an AI agent, potentially destroying substantial portions of a knowledge base. While not as severe as wiping an entire system, deletion of substantial content units warrants 'high' severity.
From the tool's definition Tool name is 'delete_book' with description 'Delete a book from BookStack.' The verb 'delete' and the irreversible nature of removing an entire book (and likely its chapters and pages) constitutes a destructive action.
Attacks that exploit this kind of access
The rule that runs delete_book safely
PolicyLayer is an MCP gateway: it sits between your AI agents and BookStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_book, this is the rule to start with:
delete_book is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect BookStack MCP Server, apply this rule, and every delete_book call is checked against it from then on.
Questions about delete_book
Delete a book from BookStack. It is categorised as a Destructive tool in the BookStack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the BookStack MCP Server MCP server in PolicyLayer and add a rule for delete_book: 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 BookStack MCP Server. Nothing to install.
delete_book is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_book 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.
Set action: deny in the PolicyLayer policy for delete_book. 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.
delete_book is provided by the BookStack MCP Server MCP server (derron-knox/bookstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on BookStack MCP Server, and thousands of servers like it.
Across the catalogue