Low Risk

get_document

get_document

How to control get_document ↓

What get_document does on Knowledge Rag

AI agents call get_document to retrieve information from Knowledge Rag without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_document needs a policy

Based on the tool name 'get_document' and the sibling tools in the knowledge-rag server (which includes search, list, add, remove, and reindex operations), this tool appears to retrieve or fetch a document from the local RAG index. This is a read operation with no side effects. The empty description reduces confidence slightly, but the clear pattern of retrieval tools on this server supports the Read classification.

From the tool's definition Tool name 'get_document' and sibling tools like 'list_documents', 'search_knowledge', and 'search_similar' indicate a local document retrieval system. The server description emphasizes search and retrieval functionality.

Documented attack patterns abuse exactly the kind of access get_document gives an agent:

How to control get_document

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_document": {}
  }
}

get_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Knowledge Rag — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_document

What does the get_document tool do? +

get_document. It is categorised as a Read tool in the Knowledge Rag MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_document? +

Register the Knowledge Rag MCP server in PolicyLayer and add a rule for get_document: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Knowledge Rag. Nothing to install.

What risk level is get_document? +

get_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_document? +

Yes. Add a rate_limit block to the get_document rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block get_document completely? +

Set action: deny in the PolicyLayer policy for get_document. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides get_document? +

get_document is provided by the Knowledge Rag MCP server (lyonzin/knowledge-rag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Knowledge Rag tool call.

Start from Knowledge Rag, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.