Get details of a specific chapter including its pages
AI agents call get_chapter 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.
This tool retrieves and queries chapter metadata and associated pages from a BookStack wiki instance. It performs no modifications, deletions, or external operations—purely informational access. The low severity reflects minimal blast radius if misused by an AI agent, as reading existing wiki content poses no direct risk to data integrity or system state.
From the tool's definition Tool name 'get_chapter' and description 'Get details of a specific chapter including its pages' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get details of a specific chapter including its pages. 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_chapter: 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_chapter 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_chapter 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_chapter. 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_chapter 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 →