bookstack_list_content
AI agents call bookstack_list_content 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.
Despite the empty description, the tool name 'list_content' combined with the server's documented support for 'content browsing' and the presence of distinct create/update/delete tools on the same server strongly indicates this retrieves or enumerates BookStack content without side effects. This is a standard Read operation with low blast radius if misused.
From the tool's definition Tool name 'bookstack_list_content' indicates a listing/querying operation. The empty description is uninformative, but the sibling tools reveal the pattern: 'list' operations are Read, while 'create/update/delete' are Write/Destructive.
Attacks that exploit this kind of access
bookstack_list_content. 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 bookstack_list_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.
bookstack_list_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 bookstack_list_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 bookstack_list_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.
bookstack_list_content is provided by the BookStack MCP Server MCP server (lborjigi/bookstack-mcp). 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 →