List all collections in a GitBook organization, optionally filtered by organization ID
AI agents call list_collections to retrieve information from GitBook 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 enumerates collections from a GitBook organization. It has no side effects, does not modify data, execute code, delete anything, or move money. The 'optionally filtered by organization ID' qualifier further confirms it is a passive query operation. Low severity because listing collections is informational only and poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'list_collections' and description 'List all collections in a GitBook organization' indicate data retrieval with no modification or execution. The verb 'list' is explicitly a Read operation per the classification rules.
Documented attack patterns abuse exactly the kind of access list_collections gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitBook MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_collections:
{
"version": "1",
"default": "deny",
"tools": {
"list_collections": {}
}
}list_collections is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all collections in a GitBook organization, optionally filtered by organization ID. It is categorised as a Read tool in the GitBook MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitBook MCP Server MCP server in PolicyLayer and add a rule for list_collections: 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 GitBook MCP Server. Nothing to install.
list_collections 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_collections 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_collections. 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_collections is provided by the GitBook MCP Server MCP server (rickysullivan/gitbook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitBook MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 GitBook MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.