bookstack_update_page
AI agents use bookstack_update_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 or modifies page data reversibly—the defining characteristic of Write category. Pages can be updated and reverted, with no permanent data loss. Severity is medium because unintended page modifications could corrupt documentation content affecting multiple users, but the operation is reversible.
From the tool's definition Tool name 'bookstack_update_page' indicates modification of existing page content. Sibling tools include 'bookstack_create_page' (Write) and 'bookstack_delete_page' (Destructive), contextualizing this as a content modification operation.
Attacks that exploit this kind of access
bookstack_update_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_update_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_update_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_update_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_update_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_update_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 →