Update an existing repository index. This re-processes all files in the repository according to the current configuration and updates the vector database.
AI agents use update_repository to create or update resources in RAG Documentation MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RAG Documentation MCP Server environment.
The tool modifies existing data (repository indexes and vector database entries) in a reversible manner. While it reprocesses files, this is an update operation that can be undone by re-running with different configuration or reverting to a previous state.
From the tool's definition Tool description states it 'Update[s] an existing repository index' and 'updates the vector database,' indicating modification of indexed data and vector records without deletion.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access update_repository gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RAG Documentation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_repository:
{
"version": "1",
"default": "deny",
"tools": {
"update_repository": {
"limits": [
{
"counter": "update_repository_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_repository 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.
Update an existing repository index. This re-processes all files in the repository according to the current configuration and updates the vector database. It is categorised as a Write tool in the RAG Documentation MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RAG Documentation MCP Server MCP server in PolicyLayer and add a rule for update_repository: 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 RAG Documentation MCP Server. Nothing to install.
update_repository 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 update_repository 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 update_repository. 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.
update_repository is provided by the RAG Documentation MCP Server MCP server (rahulretnan/mcp-ragdocs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 RAG Documentation MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 RAG Documentation MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.