wazuh-mcp

Run an active-response command

wazuh_active_response

Destructive

Run active-response commands on agents to block IPs, disable accounts, or null-route hosts. Requires write access and human confirmation before execution.

Instructions

Execute an active-response command on agents — blocking an IP with firewall-drop, disabling an account, null-routing a host. This changes the state of production endpoints and can cut off network access, so it requires WAZUH_ALLOW_WRITE=true and should be confirmed with a human before use.

Input Schema

TableJSON Schema

Name	Required	Description
`custom`	No	True when 'command' is a custom script on the agent rather than a built-in Wazuh AR command.
`command`	Yes	Command to run. Built-ins: firewall-drop, restart-wazuh, disable-account, host-deny, route-null, win_route-null, netsh. A custom script configured on the agent may also be named.
`agent_ids`	Yes	Agent IDs to run the command on. There is deliberately no 'all agents' shortcut — name the targets explicitly.
`arguments`	No	Arguments for the command, e.g. ['1.2.3.4'] as the IP to block for firewall-drop.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description transparently discloses that it is destructive and requires an explicit environment variable, matching the annotations (readOnlyHint=false, destructiveHint=true). It also warns about irreversible network impact, which is more detailed than the bare annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, with the purpose front-loaded and no redundant information. Every sentence adds value, including the risk warning and required environment variable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description conveys the essential context for a risky write operation: the purpose, the requirement for WAZUH_ALLOW_WRITE=true, and the need for human confirmation. Since an output schema exists, return values are not required, and the description suffices for agents to understand the tool's role.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers all four parameters with descriptions, so the baseline is 3. The description does not add significant extra parameter detail beyond the examples already in the schema; the 'arguments' example is echoed from the JSON schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool executes an active-response command on agents and provides concrete examples (blocking an IP, disabling an account). It uses a specific verb and resource, distinguishing it from read-only sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains that the tool changes production state and can cut off network access, and instructs that it requires WAZUH_ALLOW_WRITE=true and human confirmation before use. However, it does not explicitly contrast with sibling action tools like wazuh_restart_agents, so the when-to-use guidance is partially implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.