get_node_active_config
AI agents call get_node_active_config 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 tool appears to retrieve active node configuration from a Wazuh security system based on naming convention and server context. Retrieving configuration data is a Read operation with no side effects. Severity is medium because configuration data from security platforms could reveal sensitive system details useful for privilege escalation or lateral movement if misused by an untrusted agent.
From the tool's definition Tool name 'get_node_active_config' indicates retrieval of configuration data. No description provided, but sibling tools (get_active_configuration, get_agent_component_stats, get_agent_daemon_stats, get_agent_hardware, get_agent_hotfixes, get_agent_netaddr)…
Attacks that exploit this kind of access
get_node_active_config. 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_active_config: 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_active_config 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_active_config 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_active_config. 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_active_config 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 →