list_spaces

THE RISK

Low Risk

Why list_spaces needs a policy

This tool retrieves organizational structure information from GitBook without modifying, executing, or deleting anything. The blast radius of misuse is minimal—an agent could enumerate spaces, but cannot alter documentation or trigger external actions. Low severity is appropriate for pure data retrieval operations.

From the tool's definition Tool is named 'list_spaces' and described as 'List all spaces in a GitBook organization' — this is a query/retrieval operation with no side effects.

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

POLICY

How to control list_spaces

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_spaces": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GitBook MCP Server tools

Read get_collection Get detailed information about a specific GitBook collection Read get_collection_spaces List all spaces that belong to a specific GitBook collection Read get_file Get detailed information about a specific file uploaded to a GitBook space Read get_page_by_path Retrieve a page from a GitBook space using its path instead of page ID Read get_page_content Retrieve the content of a specific page from a GitBook space, with options for format and Read get_space Get detailed information about a specific GitBook space Read get_space_content Get the complete content structure and page hierarchy of a GitBook space Read get_space_files List all files (images, documents, etc.) uploaded to a GitBook space

All 12 GitBook MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_spaces

What does the list_spaces tool do? +

List all spaces 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.

How do I enforce a policy on list_spaces? +

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

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

Can I rate-limit list_spaces? +

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

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

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

CHECK YOUR STACK →