AI agents call wazuh_cluster_node_stats to retrieve information from Wazuh without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
No description provided, lowering confidence slightly. However, sibling tools like 'wazuh_cluster_status', 'wazuh_agent_health', and 'wazuh_alert_summary' are all Read operations that retrieve system status/metrics without side effects. This tool follows the same pattern—retrieving cluster node statistics is a non-destructive query operation.
From the tool's definition Tool name 'wazuh_cluster_node_stats' indicates retrieval of cluster node statistics. The 'stats' suffix and context within a monitoring/SIEM platform suggest querying operational metrics rather than modifying or executing operations.
Attacks that exploit this kind of access
wazuh_cluster_node_stats. It is categorised as a Read tool in the Wazuh MCP Server, which means it retrieves data without modifying state.
Register the Wazuh MCP server in PolicyLayer and add a rule for wazuh_cluster_node_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. Nothing to install.
wazuh_cluster_node_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 wazuh_cluster_node_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 wazuh_cluster_node_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.
wazuh_cluster_node_stats is provided by the Wazuh MCP server (sbharadwaj05/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 →