This record as markdown: /tools/kh0pper-crow/crow-bookstack-chapters.md
What crow_bookstack_chapters does on Crow
AI agents call crow_bookstack_chapters to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crow_bookstack_chapters is rated Low
This tool queries and retrieves chapter metadata from a BookStack book. It performs a read-only operation that returns information without altering, deleting, or executing any external logic. No financial, destructive, or code execution capabilities are involved. The risk is low because the action is informational only.
From the tool's definition Tool name contains 'list' verb and description states 'List chapters in a BookStack book' — a straightforward data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs crow_bookstack_chapters safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_bookstack_chapters, this is the rule to start with:
crow_bookstack_chapters 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 Crow, apply this rule, and every crow_bookstack_chapters call is checked against it from then on.
Questions about crow_bookstack_chapters
List chapters in a BookStack book. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_bookstack_chapters: 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 Crow. Nothing to install.
crow_bookstack_chapters 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 crow_bookstack_chapters 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 crow_bookstack_chapters. 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.
crow_bookstack_chapters is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue