Get statistics for vector indices.
AI agents call ruvector_index_stats to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries statistics—metadata about vector indices. It performs no side effects, does not execute code or commands, does not modify data, and does not delete anything. It is a straightforward read operation.
From the tool's definition Tool name 'ruvector_index_stats' and description 'Get statistics for vector indices' indicate a retrieval operation that queries metadata about existing vector indices without modifying or executing operations.
Attacks that exploit this kind of access
Get statistics for vector indices. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for ruvector_index_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 Claude Flow. Nothing to install.
ruvector_index_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 ruvector_index_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 ruvector_index_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.
ruvector_index_stats is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.