get_node_daemon_stats
AI agents call get_node_daemon_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 naming convention and context of similar tools on the Wazuh MCP server indicate this is a query/retrieval operation for daemon statistics. No description was provided, which lowers confidence slightly, but the consistent 'get_' pattern and the security monitoring context (reading stats, not modifying systems) classify this as Read with low severity.
From the tool's definition Tool name 'get_node_daemon_stats' uses the 'get' verb, indicating data retrieval. Description is empty, but sibling tools like 'get_agent_daemon_stats', 'get_agent_hardware', 'get_agent_hotfixes', and 'get_agent_key' are all consistent with Read operations…
Attacks that exploit this kind of access
get_node_daemon_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_node_daemon_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_node_daemon_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_node_daemon_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_node_daemon_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_node_daemon_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 →