Return the status of all Wazuh daemons in the specified node.
AI agents call get_node_status 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.
This tool retrieves status information about running daemons in a Wazuh node. It is purely informational, performing a read-only query without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an AI agent could retrieve unwanted status information but cannot modify system state or trigger operations.
From the tool's definition Tool name 'get_node_status' and description 'Return the status of all Wazuh daemons in the specified node' indicate a query/retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Return the status of all Wazuh daemons in the specified node. 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_status: 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_status 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_status 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_status. 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_status 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 →