Search across all content types (books, chapters, pages, shelves) in BookStack
AI agents call search_all 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.
Search functionality retrieves and queries data without side effects. This is a classic Read operation that presents minimal risk—an AI agent misusing it would at worst waste compute or retrieve inappropriate information, but cannot modify, delete, or execute operations. The low blast radius justifies 'low' severity.
From the tool's definition Tool is named 'search_all' and described as 'Search across all content types (books, chapters, pages, shelves) in BookStack'. The verb 'search' and absence of any modification, deletion, or execution language indicate a query-only operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Search across all content types (books, chapters, pages, shelves) in BookStack. 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 search_all: 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.
search_all 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 search_all 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 search_all. 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.
search_all 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 →