// SCAN REPORT

RAG Documentation MCP Server

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

2 destructive tools with no built-in limits. Policy required.

Last updated: 1 Jul 2026

3 can modify or destroy data

4 read-only

7 tools total

Community server · catalogue entry verified 01/07/2026

How to control RAG Documentation MCP Server ↓

TOOL MAP

What RAG Documentation MCP Server exposes to your agents

Read (4) Write / Execute (1) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous RAG Documentation MCP Server tools

Destructive · High clear_queue This tool permanently removes data (queued URLs) that cannot be recovered without manual re-entry. Destructive · High remove_documentation While the tool removes documentation rather than user data, the removal is permanent and irreversible, affecting the system's knowledge base and future search results. Execute · Medium run_queue This tool executes a defined workflow that fetches and processes multiple external URLs, performing indexing operations.

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

POLICY

How to control RAG Documentation MCP Server

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

Deny destructive operations

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

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

Cap read operations

{
  "extract_urls": {
    "limits": [
      {
        "counter": "extract_urls_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 RAG Documentation 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 RAG DOCUMENTATION →

Instant setup, no code required.

FULL CATALOGUE

All 7 RAG Documentation MCP Server tools

DESTRUCTIVE 2 tools

Destructive clear_queue Remove all pending URLs from the documentation processing queue. Use this to reset the queue when you want to Destructive remove_documentation Remove specific documentation sources from the system by their URLs. Use this tool to clean up outdated docume

EXECUTE 1 tools

Execute run_queue Process and index all URLs currently in the documentation queue. Each URL is processed sequentially, with prop

READ 4 tools

Read extract_urls Extract and analyze all URLs from a given web page. This tool crawls the specified webpage, identifies all hyp Read list_queue List all URLs currently waiting in the documentation processing queue. Shows pending documentation sources tha Read list_sources List all documentation sources currently stored in the system. Returns a comprehensive list of all indexed doc Read search_documentation Search through stored documentation using natural language queries. Use this tool to find relevant information

EXPLORE

Related servers

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

FAQ

Questions about RAG Documentation MCP Server

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

Yes. The RAG Documentation MCP Server server exposes 2 destructive tools including clear_queue, remove_documentation. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the RAG Documentation MCP Server MCP server expose? +

7 tools across 3 categories: Destructive, Execute, Read. 4 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on RAG Documentation MCP Server? +

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

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

ENFORCE POLICY ON RAG DOCUMENTATION →

Instant setup, no code required.

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