get_index_stats
AI agents call get_index_stats to retrieve information from Wazuh MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and context suggest this retrieves statistical data about indices (likely Elasticsearch indices given Wazuh's architecture), which is a read-only operation with no side effects. The empty description lowers confidence slightly, but the naming convention and position among other query/retrieval tools strongly indicate a Read category. No modification, execution, or destructive capability is evident.
From the tool's definition Tool name 'get_index_stats' indicates retrieval of index statistics; described as part of a security platform's monitoring and analysis capabilities alongside sibling tools like 'count_documents' and 'get_agent_*' which are clearly read-only queries.
Attacks that exploit this kind of access
get_index_stats. It is categorised as a Read tool in the Wazuh MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wazuh MCP Server MCP server in PolicyLayer and add a rule for get_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 Wazuh MCP Server. Nothing to install.
get_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 get_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 get_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.
get_index_stats is provided by the Wazuh MCP Server MCP server (rayasatriatama/wazuh-mcp-server). 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 →