Create a new page in a book or chapter
AI agents use create_page 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.
The tool creates new content (a wiki page) which is a Write operation. Severity is medium because the blast radius depends on context—an AI could create numerous unwanted pages or pages with malicious content, but the operation is reversible via deletion. It does not irreversibly destroy data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read (Read).
From the tool's definition Tool name 'create_page' and description 'Create a new page in a book or chapter' directly indicate data creation. This is a reversible write operation.
Attacks that exploit this kind of access
Create a new page in a book or chapter. 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_page: 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_page 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_page 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_page. 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_page 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 →