Get index statistics including chunk count, vector count, and source count
AI agents call stats to retrieve information from IndexFoundry MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistical information (counts and metrics) from an index. It has no side effects, does not modify data, execute commands, delete records, or involve financial transactions. It is a pure read operation that fetches pre-computed or aggregated metadata, making it low severity with high confidence.
From the tool's definition Tool name 'stats' and description 'Get index statistics including chunk count, vector count, and source count' indicates a retrieval operation that queries aggregated metadata about an index without modification, deletion, or execution of operations.
Attacks that exploit this kind of access
Get index statistics including chunk count, vector count, and source count. It is categorised as a Read tool in the IndexFoundry MCP MCP Server, which means it retrieves data without modifying state.
Register the IndexFoundry MCP server in PolicyLayer and add a rule for 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 IndexFoundry MCP. Nothing to install.
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 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 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.
stats is provided by the IndexFoundry MCP server (mnehmos/mnehmos.index-foundry.mcp). 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 →