Add documents from directory path or file path for RAG embedding and store to DB. Supported file types: .json, .jsonl, .txt, .md, .csv
AI agents use embedding_documents to create or update resources in Mcp Rag — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Rag environment.
This tool creates and stores new data (document embeddings) in a database, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or cause financial impact.
From the tool's definition Tool description states it 'Add documents from directory path or file path for RAG embedding and store to DB', which modifies the RAG database by creating new indexed records.
Documented attack patterns abuse exactly the kind of access embedding_documents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for embedding_documents:
{
"version": "1",
"default": "deny",
"tools": {
"embedding_documents": {
"limits": [
{
"counter": "embedding_documents_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}embedding_documents 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.
Free to start. No card required.
Add documents from directory path or file path for RAG embedding and store to DB. Supported file types: .json, .jsonl, .txt, .md, .csv. It is categorised as a Write tool in the Mcp Rag MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Rag MCP server in PolicyLayer and add a rule for embedding_documents: 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. Nothing to install.
embedding_documents 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 embedding_documents 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 embedding_documents. 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.
embedding_documents is provided by the Mcp Rag MCP server (kwanleefrmvi/mcp-rag-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp 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.
5 Mcp Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.