Get statistics about the RAG system, including number of documents and chunks.
AI agents call get_rag_stats to retrieve information from RAG Document Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves aggregate statistics about the RAG system's state (document count, chunk count). It performs no write operations, does not execute code or external operations, and cannot delete or modify data. The blast radius of misuse is minimal—an AI agent obtaining system statistics poses negligible risk. This is a pure read/query operation.
From the tool's definition Tool name 'get_rag_stats' and description 'Get statistics about the RAG system, including number of documents and chunks' indicate a retrieval operation with no modification or destructive capability.
Attacks that exploit this kind of access
Get statistics about the RAG system, including number of documents and chunks. It is categorised as a Read tool in the RAG Document Server MCP Server, which means it retrieves data without modifying state.
Register the RAG Document Server MCP server in PolicyLayer and add a rule for get_rag_stats: 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 Document Server. Nothing to install.
get_rag_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_rag_stats 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 get_rag_stats. 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.
get_rag_stats is provided by the RAG Document Server MCP server (jaimeferj/mcp-rag-docs). 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 →