This record as markdown: /tools/derron-knox-bookstack-mcp-server/delete-page.md
What delete_page does on BookStack MCP Server
AI agents call 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.
Why delete_page is rated Critical
Deletion operations that permanently remove data fall into the Destructive category, which ranks above Execute and Write. The blast radius is high because an AI agent with access to this tool could accidentally or maliciously delete pages from a knowledge base without recovery. Confidence is high due to explicit naming and clear destructive intent.
From the tool's definition Tool name 'delete_page' and description 'Delete a page' indicate irreversible deletion of data. This is a destructive operation that cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete_page 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 delete_page, this is the rule to start with:
delete_page is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect BookStack MCP Server, apply this rule, and every delete_page call is checked against it from then on.
Questions about delete_page
Delete a page. 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 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.
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 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 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.
delete_page 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.
Across the catalogue