AI agents invoke wazuh_run_active_response to trigger actions in Wazuh. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Active response tools execute commands on monitored systems and can trigger security operations with real-world side effects (firewall blocks, process termination, etc.). This is Execute-category because it runs operations whose effects depend on arguments and cannot always be trivially undone.
From the tool's definition Tool name 'wazuh_run_active_response' indicates execution of active response actions; 'run' and 'active response' are action verbs that trigger external operations.
Attacks that exploit this kind of access
wazuh_run_active_response. It is categorised as a Execute tool in the Wazuh MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wazuh MCP server in PolicyLayer and add a rule for wazuh_run_active_response: 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_run_active_response is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wazuh_run_active_response 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_run_active_response. 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_run_active_response 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 →