AI agents use add_document to create or update resources in Knowledge Rag — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Knowledge Rag environment.
The name 'add_document' indicates a write operation that creates or stores data in the knowledge base. This is reversible (documents can be removed via remove_document), so it does not qualify as Destructive. While the empty description lowers confidence, the consistent naming pattern with sibling tools and the server's stated purpose as a 'Local RAG system' support Write classification.
From the tool's definition Tool name 'add_document' implies document creation/ingestion. Description is empty, limiting direct evidence.
Documented attack patterns abuse exactly the kind of access add_document gives an agent:
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 add_document:
{
"version": "1",
"default": "deny",
"tools": {
"add_document": {
"limits": [
{
"counter": "add_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_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.
Free to start. No card required.
add_document. It is categorised as a Write tool in the Knowledge Rag MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Knowledge Rag MCP server in PolicyLayer and add a rule for add_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.
add_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 add_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 add_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.
add_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.
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.