Export a page in various formats
AI agents call export_page to retrieve information from BookStack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting a page retrieves existing content and converts it to a desired format (e.g., PDF, HTML, plain text). This is a read-only operation with no side effects on the data stored in BookStack.
From the tool's definition Export a page in various formats
Attacks that exploit this kind of access
Export a page in various formats. It is categorised as a Read tool in the BookStack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BookStack MCP Server MCP server in PolicyLayer and add a rule for export_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.
export_page is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the export_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 export_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.
export_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 →