bookstack_create_page
AI agents use bookstack_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.
This tool creates new pages in BookStack, modifying the documentation state reversibly. It falls under Write rather than Read (creates data), Execute (no arbitrary code execution), or Destructive (creation is reversible—pages can be deleted). Severity is medium because uncontrolled page creation could clutter documentation but does not cause permanent loss of data or financial impact.
From the tool's definition Tool name 'bookstack_create_page' combined with server description stating it supports 'CRUD operations for books, chapters, and pages'. The sibling tools include create/delete/update operations, confirming this is a write operation.
Attacks that exploit this kind of access
bookstack_create_page. 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 bookstack_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.
bookstack_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 bookstack_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 bookstack_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.
bookstack_create_page is provided by the BookStack MCP Server MCP server (lborjigi/bookstack-mcp). 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 →