Delete a page from BookStack.
AI agents call bookstack_delete_page 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.
The tool permanently removes a page from BookStack documentation, which cannot be undone. While not financial or system-critical, deletion of documentation pages can impact knowledge availability and business continuity. The severity is high rather than critical because impact is typically scoped to a single page unless an agent is given unbounded iteration.
From the tool's definition Tool name explicitly includes 'delete' and description states 'Delete a page from BookStack'. This is an irreversible operation that removes data.
Attacks that exploit this kind of access
Delete a page 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.
Register the BookStack MCP Server MCP server in PolicyLayer and add a rule for bookstack_delete_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_delete_page is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bookstack_delete_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_delete_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_delete_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 →