index_document
Index a document into the knowledge base. The document will be chunked and embedded automatically.
This record as markdown: /tools/0xrdan-mcp-rag-server/index-document.md
What index_document does on MCP RAG Server
AI agents use index_document to create or update resources in MCP RAG Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP RAG Server environment.
Why index_document is rated Medium
This tool creates new data (document chunks and embeddings) in the ChromaDB vector store. It is a write operation — adding/modifying the knowledge base contents — but it is reversible since sibling tools like delete_by_source can remove indexed documents. No code execution, deletion, or financial action is involved.
From the tool's definition 'Index a document into the knowledge base. The document will be chunked and embedded automatically.'
Attacks that exploit this kind of access
The rule that runs index_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP RAG Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For index_document, this is the rule to start with:
index_document stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP RAG Server, apply this rule, and every index_document call is checked against it from then on.
Questions about index_document
Index a document into the knowledge base. The document will be chunked and embedded automatically. It is categorised as a Write tool in the MCP RAG Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP RAG Server MCP server in PolicyLayer and add a rule for index_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 MCP RAG Server. Nothing to install.
index_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the index_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.
Set action: deny in the PolicyLayer policy for index_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.
index_document is provided by the MCP RAG Server MCP server (0xrdan/mcp-rag-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP RAG Server, and thousands of servers like it.
This server
Across the catalogue