// SCAN REPORT

Knowledge Rag

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

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

Last updated: 11 Jun 2026

6 can modify or destroy data

6 read-only

12 tools total

Community server · catalogue entry verified 11/06/2026

How to control Knowledge Rag ↓

TOOL MAP

What Knowledge Rag exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Knowledge Rag tools

Destructive · High remove_document While the primary action of removing a document from the index could be considered Write (reversible modification), the optional delete_file parameter enables permanent, irreversible deletion of files from disk. Write · High reindex_documents The primary action is rebuilding/modifying the vector index, which is a Write operation. Write · Medium add_document The name 'add_document' indicates a write operation that creates or stores data in the knowledge base. Write · Medium add_from_url This tool creates and modifies data in the knowledge base by fetching external content and persisting it.

6 of Knowledge Rag'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 Knowledge Rag

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

Deny destructive operations

{
  "remove_document": {
    "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

{
  "reindex_documents": {
    "limits": [
      {
        "counter": "reindex_documents_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_document": {
    "limits": [
      {
        "counter": "get_document_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 Knowledge Rag — 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 KNOWLEDGE RAG →

Free to start. No card required.

FULL CATALOGUE

All 12 Knowledge Rag tools

DESTRUCTIVE 1 tools

Destructive remove_document Remove a document from the knowledge base index. Mutating — removes index entries. If delete_file=True, a

WRITE 4 tools

Write reindex_documents Index or reindex all documents in the knowledge base. Mutating — modifies the vector index. CPU/IO intens Write add_document add_document Write add_from_url Fetch content from a URL, convert to markdown, and add to the knowledge base. Mutating — makes an outboun Write update_document Update the content of an existing document in the knowledge base. Mutating — overwrites the file on disk

READ 6 tools

Read get_document get_document Read get_index_stats Get statistics and health metrics for the knowledge base index. Read-only. No side effects. Returns: Read list_documents List all indexed documents, optionally filtered by category. Read-only. No side effects. Args: Read search_knowledge Hybrid search combining semantic search + BM25 keyword search with cross-encoder reranking. Read-only. No Read search_similar search_similar

OTHER 1 tools

Other evaluate_retrieval evaluate_retrieval

EXPLORE

Related servers

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

FAQ

Questions about Knowledge Rag

Can an AI agent delete data through the Knowledge Rag MCP server? +

Yes. The Knowledge Rag server exposes 1 destructive tools including remove_document. 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 Knowledge Rag? +

The Knowledge Rag server has 4 write tools including reindex_documents, add_document, add_from_url. 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 Knowledge Rag.

How many tools does the Knowledge Rag MCP server expose? +

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

How do I enforce a policy on Knowledge Rag? +

Register the Knowledge Rag 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 Knowledge Rag tool call.

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

ENFORCE POLICY ON KNOWLEDGE RAG →

Free to start. No card required.

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