create_chapter
Create a new chapter in BookStack.
This record as markdown: /tools/derron-knox-bookstack-mcp-server/create-chapter.md
What create_chapter does on BookStack MCP Server
AI agents use create_chapter to create or update resources in BookStack MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BookStack MCP Server environment.
Why create_chapter is rated Medium
Creating a chapter is a reversible modification operation—chapters can be deleted or edited afterward. It does not irreversibly destroy data, execute arbitrary code, move money, or read data. The blast radius is medium: an AI agent could create unwanted chapters, polluting the knowledge base, but the damage is recoverable via the delete_chapter tool also present on this server.
From the tool's definition Tool name 'create_chapter' and description 'Create a new chapter in BookStack' directly indicate data creation. The sibling tools confirm this is a write-capable server (alongside create_page, create_book, create_shelf).
Attacks that exploit this kind of access
The rule that runs create_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 create_chapter, this is the rule to start with:
create_chapter stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect BookStack MCP Server, apply this rule, and every create_chapter call is checked against it from then on.
Questions about create_chapter
Create a new chapter in BookStack. It is categorised as a Write tool in the BookStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BookStack MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_chapter is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.
This server
Across the catalogue