Low Risk

get_collection

Get detailed information about a specific GitBook collection

How to control get_collection ↓

What get_collection does on GitBook MCP Server

AI agents call get_collection 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.

Low Risk

Why get_collection needs a policy

This tool queries and retrieves metadata about a collection without creating, modifying, deleting, or executing anything. It is a straightforward information retrieval operation typical of documentation access APIs. Severity is low because exposure of collection metadata carries minimal blast radius—no data is altered, and the information is typically intended to be accessible within the organization.

From the tool's definition Tool description states 'Get detailed information about a specific GitBook collection' — a retrieval operation with no modification or execution.

Documented attack patterns abuse exactly the kind of access get_collection gives an agent:

How to control get_collection

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 get_collection:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_collection": {}
  }
}

get_collection is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GitBook MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_collection

What does the get_collection tool do? +

Get detailed information about a specific GitBook collection. It is categorised as a Read tool in the GitBook MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_collection? +

Register the GitBook MCP Server MCP server in PolicyLayer and add a rule for get_collection: 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.

What risk level is get_collection? +

get_collection is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_collection? +

Yes. Add a rate_limit block to the get_collection 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.

How do I block get_collection completely? +

Set action: deny in the PolicyLayer policy for get_collection. 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.

What MCP server provides get_collection? +

get_collection 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.

Enforce policy on every GitBook MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.