delete_chapter
Delete a chapter from BookStack.
This record as markdown: /tools/derron-knox-bookstack-mcp-server/delete-chapter.md
What delete_chapter does on BookStack MCP Server
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.
Why delete_chapter is rated Critical
Deletion operations are irreversible and fall under the Destructive category. Removing a chapter from a knowledge base cannot be undone without restore mechanisms, affecting potentially significant content and dependent references. While not financial or system-critical, the data loss impact justifies 'high' severity for typical knowledge base contexts.
From the tool's definition Tool name is 'delete_chapter' and description explicitly states 'Delete a chapter from BookStack.' The verb 'delete' combined with 'chapter' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_chapter 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_chapter, this is the rule to start with:
delete_chapter 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_chapter call is checked against it from then on.
Questions about delete_chapter
Delete a chapter 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_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 (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