// SCAN REPORT

DevDocs MCP Server

12 tools. 2 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 29 Jun 2026

2 can modify or destroy data

10 read-only

12 tools total

Community server · catalogue entry verified 29/06/2026

How to control DevDocs MCP Server ↓

TOOL MAP

What DevDocs MCP Server exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous DevDocs MCP Server tools

Destructive · Medium clear_cache Clearing a cache is a destructive operation that removes stored data without a simple undo mechanism. Write · Medium export_documentation export_documentation

2 of DevDocs MCP Server's 12 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control DevDocs MCP Server

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

Deny destructive operations

{
  "clear_cache": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "export_documentation": {
    "limits": [
      {
        "counter": "export_documentation_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_cache_stats": {
    "limits": [
      {
        "counter": "get_cache_stats_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 DevDocs 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 DEVDOCS →

Instant setup, no code required.

FULL CATALOGUE

All 12 DevDocs MCP Server tools

DESTRUCTIVE 1 tools

Destructive clear_cache clear_cache

WRITE 1 tools

Write export_documentation export_documentation

READ 10 tools

Read get_cache_stats get_cache_stats Read get_documentation_index get_documentation_index Read get_examples get_examples Read get_multiple_pages get_multiple_pages Read get_page_content get_page_content Read get_type_entries get_type_entries Read list_documentations list_documentations Read offline_mode_status offline_mode_status Read search_across_docs search_across_docs Read search_documentation search_documentation

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about DevDocs MCP Server

Can an AI agent delete data through the DevDocs MCP Server MCP server? +

Yes. The DevDocs MCP Server server exposes 1 destructive tools including clear_cache. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through DevDocs MCP Server? +

The DevDocs MCP Server server has 1 write tools including export_documentation. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach DevDocs MCP Server.

How many tools does the DevDocs MCP Server MCP server expose? +

12 tools across 3 categories: Destructive, Read, Write. 10 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on DevDocs MCP Server? +

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

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

ENFORCE POLICY ON DEVDOCS →

Instant setup, no code required.

12 DevDocs MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.