Low Risk

list_organizations

List all GitBook organizations accessible with the current API token

How to control list_organizations ↓

What list_organizations does on GitBook MCP Server

AI agents call list_organizations 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 list_organizations needs a policy

This tool performs a read-only query that lists organizations. It retrieves information without creating, modifying, deleting, or executing any operations. The action is passive data retrieval with minimal blast radius if misused by an AI agent — it would only expose organizational metadata already accessible to the authenticated token.

From the tool's definition Tool name is 'list_organizations' and description states 'List all GitBook organizations accessible with the current API token' — retrieves and enumerates data with no modification or side effects.

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

How to control list_organizations

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

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

list_organizations 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 list_organizations

What does the list_organizations tool do? +

List all GitBook organizations accessible with the current API token. 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 list_organizations? +

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

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

Can I rate-limit list_organizations? +

Yes. Add a rate_limit block to the list_organizations 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 list_organizations completely? +

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

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