This record as markdown: /tools/derron-knox-bookstack-mcp-server/list-books.md
What list_books does on BookStack MCP Server
AI agents call list_books 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 list_books is rated Low
This tool queries and retrieves a list of books from the BookStack knowledge base. It performs no creation, modification, deletion, or execution of commands. The operation is read-only and has no destructive, financial, or execution implications. Even in a multi-tenant or sensitive context, listing books is a foundational read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_books' and description 'List all books' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_books 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 list_books, this is the rule to start with:
list_books 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 list_books call is checked against it from then on.
Questions about list_books
List all books. 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 list_books: 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.
list_books 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 list_books 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 list_books. 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.
list_books 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