get_nodes_info
AI agents call get_nodes_info 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.
Based on the tool name and consistent naming patterns with sibling tools that are clearly information retrieval operations (get_*), this tool appears to query node information from the Wazuh platform without modifying state. The empty description lowers confidence slightly, but the 'get_' prefix and context among other read-only tools strongly suggest a Read category with low severity.
From the tool's definition Tool name 'get_nodes_info' indicates a retrieval operation. The description is empty, but the naming pattern matches other sibling tools (get_agent_*, get_active_configuration) that are all retrieval-focused information queries.
Attacks that exploit this kind of access
get_nodes_info. 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_nodes_info: 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_nodes_info 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_nodes_info 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_nodes_info. 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_nodes_info 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 →