get_page_content
Get the content of a specific page.
This record as markdown: /tools/derron-knox-bookstack-mcp-server/get-page-content.md
What get_page_content does on BookStack MCP Server
AI agents call get_page_content to retrieve information from BookStack MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_page_content is rated Low
This tool queries and retrieves page content from BookStack without creating, modifying, deleting, or executing any operations. It has no side effects beyond data retrieval, making it a Read operation with low severity.
From the tool's definition Tool name 'get_page_content' and description 'Get the content of a specific page' indicate a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs get_page_content 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 get_page_content, this is the rule to start with:
get_page_content is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect BookStack MCP Server, apply this rule, and every get_page_content call is checked against it from then on.
Questions about get_page_content
Get the content of a specific page. 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 get_page_content: 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.
get_page_content 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 get_page_content 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 get_page_content. 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.
get_page_content 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.
This server
Across the catalogue