// SCAN REPORT

Guide Registry

10 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 11 Oct 2026

0 can modify or destroy data

10 read-only

10 tools total

Community server · catalogue entry checked 11/10/2026 · full schemas captured for 9 of 10 tools

How to control Guide Registry ↓

TOOL MAP

What Guide Registry exposes to your agents

Read (10) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Guide Registry costs in tokens

2,119 tokens of tool definitions, loaded on every request

1.1% of a 200k context window

555 heaviest tool: list_guides

Full per-tool breakdown → Model it in the token calculator →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Guide Registry

PolicyLayer is an MCP gateway — it sits between your AI agents and Guide Registry, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "get_answer": {
    "limits": [
      {
        "counter": "get_answer_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Guide Registry — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GUIDE REGISTRY →

Instant setup, no code required.

FULL CATALOGUE

All 10 Guide Registry tools

READ 10 tools

Read get_answer Get one Answer — question, grounded answer, visible citations — by id or slug, in the Answer contract v0 shape Read get_guide Get one guide's registry row by slug, with its artifact + routing-surface status. Read list_answers List Answers (contract v0), paginated with an opaque cursor. Read-only. Read list_capabilities Traverse the capability spine joining books, guides (capability packages), KSAO-grade elements and jobs. Use m Read list_conditions List organizational conditions (identity, label, guide count, causal-role counts). Filter by draft domain, sub Read list_disagreements Where does the field disagree? Returns cross-book tension names and the books on each pole (title, author, lib Read list_guides List the bicycle.guide registry — every guide's home, status, access, standard, syndication and grounding, plu Read list_taxonomy Get the bicycle.guide vocabulary — domains, shelves (with live guide counts), series, personas, guide_types, a Read search_answers Search Answers by free-text query over question/answer text. Returns contract v0 records. Read-only. Read search_guides Search published guides by topic. Returns matches, or a structured refusal with the nearest owned guides and t

FAQ

Questions about Guide Registry

Is the Guide Registry MCP server safe to use without restrictions? +

The Guide Registry server is primarily read-only with 10 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Guide Registry MCP server expose? +

10 tools across 1 categories: Read. 10 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Guide Registry? +

Register the Guide Registry MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Guide Registry tool call.

Deterministic rules across all 10 Guide Registry tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GUIDE REGISTRY →

Instant setup, no code required.

10 Guide Registry tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Guide Registry's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →