Clear and refresh the entire document index
AI agents call refresh_index to permanently remove resources in MCP RAG Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes all documents from the vector index without an undo mechanism. While not a direct data loss of the source documents, it destroys the indexed knowledge base that the RAG system depends on. This is irreversible and prevents subsequent search/retrieval operations until documents are re-ingested. An AI agent invoking this unexpectedly would cause significant operational disruption.
From the tool's definition 'Clear and refresh the entire document index' - the term 'clear' indicates irreversible deletion of all indexed documents from ChromaDB vector storage.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear and refresh the entire document index. It is categorised as a Destructive tool in the MCP RAG Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP RAG Server MCP server in PolicyLayer and add a rule for refresh_index: 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.
refresh_index is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the refresh_index 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 refresh_index. 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.
refresh_index is provided by the MCP RAG Server MCP server (luizdopc/mcp-rag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →