New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_chapter

Delete a chapter from BookStack.

SERVERBookStack MCP Server SOURCEderron-knox/bookstack-mcp-server
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/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.

Questions about delete_chapter

What does the delete_chapter tool do? +

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.

How do I enforce a policy on delete_chapter? +

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.

What risk level is delete_chapter? +

delete_chapter 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 delete_chapter? +

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.

How do I block delete_chapter completely? +

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.

What MCP server provides delete_chapter? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of BookStack MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.