Get indexing statistics (repositories, documents, chunks)
AI agents call get_stats to retrieve information from Embeddings Searcher without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only tool that queries and returns statistical information about the embedding system's state. It has no side effects, cannot modify data, and presents minimal risk even if misused by an AI agent, as it only exposes aggregate counts and metadata about the indexing process.
From the tool's definition Tool retrieves indexing statistics (repositories, documents, chunks) with no modification capability mentioned. The description indicates it only reports metrics about the indexed content.
Attacks that exploit this kind of access
Get indexing statistics (repositories, documents, chunks). It is categorised as a Read tool in the Embeddings Searcher MCP Server, which means it retrieves data without modifying state.
Register the Embeddings Searcher MCP server in PolicyLayer and add a rule for get_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 Embeddings Searcher. Nothing to install.
get_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_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_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_stats is provided by the Embeddings Searcher MCP server (thypon/kb). 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 →