Delete a chapter (moves to recycle bin)
AI agents call delete_chapter 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.
Deletion of wiki chapters constitutes destructive action. Although BookStack may provide recovery via recycle bin, the immediate effect is removal of content from active use. In a multi-user wiki context, deleting a chapter can impact multiple dependent pages and user workflows.
From the tool's definition Tool name is 'delete_chapter' and description states 'Delete a chapter'. While the description notes it 'moves to recycle bin' (suggesting potential recovery), the primary action is deletion of a chapter, which is an irreversible removal of structured content…
Attacks that exploit this kind of access
Delete a chapter (moves to recycle bin). 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_chapter: 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_chapter 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_chapter 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_chapter. 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_chapter is provided by the BookStack MCP Server MCP server (lautarobarba/bookstack_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →