get_cluster_stats
AI agents call get_cluster_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 'get_' prefix combined with 'stats' (statistics) strongly indicates this retrieves monitoring/analytics data without modification. Given the Wazuh platform context and similar sibling tools that query system and agent information, this is classified as a Read operation with low severity blast radius—misuse would only expose operational data, not enable attacks or data modification.
From the tool's definition Tool name 'get_cluster_stats' uses verb 'get' indicating data retrieval. Empty description limits certainty, but contextual sibling tools (get_agent_component_stats, get_agent_daemon_stats, get_agent_hardware, get_agent_hotfixes, get_agent_netaddr) are all…
Attacks that exploit this kind of access
get_cluster_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_cluster_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_cluster_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_cluster_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_cluster_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_cluster_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 →