// SCAN REPORT

Rust Docs MCP Server

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

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

Last updated: 11 Jun 2026

0 can modify or destroy data

7 read-only

7 tools total

Community server · catalogue entry verified 11/06/2026

How to control Rust Docs MCP Server ↓

TOOL MAP

What Rust Docs MCP Server exposes to your agents

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

Running more than one server? Check your whole stack →

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 Rust Docs MCP Server

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

Cap read operations

{
  "get_crate_documentation": {
    "limits": [
      {
        "counter": "get_crate_documentation_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 Rust Docs MCP Server — 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 RUST DOCS →

Free to start. No card required.

FULL CATALOGUE

All 7 Rust Docs MCP Server tools

READ 7 tools

Read get_crate_documentation get_crate_documentation Read get_crate_versions get_crate_versions Read get_feature_flags get_feature_flags Read get_source_code get_source_code Read get_type_info get_type_info Read search_crates search_crates Read search_symbols search_symbols

FAQ

Questions about Rust Docs MCP Server

Is the Rust Docs MCP Server MCP server safe to use without restrictions? +

The Rust Docs MCP Server server is primarily read-only with 7 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 Rust Docs MCP Server MCP server expose? +

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

How do I enforce a policy on Rust Docs MCP Server? +

Register the Rust Docs MCP Server 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 Rust Docs MCP Server tool call.

Deterministic rules across all 7 Rust Docs MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON RUST DOCS →

Free to start. No card required.

7 Rust Docs MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.