// SCAN REPORT

Wazuh

28 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated:

0 can modify or destroy data
28 read-only
28 tools total

Community server · catalogue entry verified 29/06/2026

How to control Wazuh ↓

TOOL MAP

What Wazuh exposes to your agents

Read (28) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

✕

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Wazuh

PolicyLayer is an MCP gateway — it sits between your AI agents and Wazuh, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations
{
  "diagnose_wazuh_connection": {
    "limits": [
      {
        "counter": "diagnose_wazuh_connection_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Wazuh — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON WAZUH →

Instant setup, no code required.

FULL CATALOGUE

All 28 Wazuh tools

READ 28 tools
Read diagnose_wazuh_connection Check Wazuh MCP configuration and connectivity without exposing credentials Read get_agent Get detailed information about a specific Wazuh agent by ID Read get_agent_hotfixes List Windows hotfixes/patches installed on a Wazuh agent Read get_agent_network List network interfaces and their IP addresses on a Wazuh agent Read get_agent_os Get operating system information collected from a Wazuh agent Read get_agent_packages List software packages installed on a Wazuh agent Read get_agent_ports List open network ports on a Wazuh agent Read get_agent_processes List running processes on a Wazuh agent Read get_agent_stats Get system statistics (CPU, memory, disk) for a specific Wazuh agent Read get_alert Retrieve a single security alert by its ID. Fields such as rule_description, full_log, and data carry attacker Read get_alerts Retrieve recent security alerts from Wazuh with optional filtering. Fields such as rule_description and full_l Read get_fim_files Get File Integrity Monitoring (FIM) results for a Wazuh agent — shows monitored files, registry keys, and dete Read get_group_agents List agents belonging to a specific Wazuh group Read get_manager_config Get the active Wazuh manager configuration for a specific section Read get_manager_logs Retrieve Wazuh manager logs with optional filtering by severity level or module tag. Log description values ca Read get_rootcheck Get rootkit detection scan results for a Wazuh agent Read get_rule Get detailed information about a specific Wazuh rule by ID Read get_sca_checks Get individual check results for a specific SCA policy on a Wazuh agent Read get_sca_policies List Security Configuration Assessment (SCA) policies evaluated on a Wazuh agent Read get_wazuh_version Get the Wazuh manager version and API information Read list_agents List all Wazuh agents with optional status filtering Read list_decoders List all available Wazuh decoders with optional name filtering Read list_groups List all Wazuh agent groups Read list_rules List all Wazuh rules with optional level and group filtering Read list_vulnerabilities List Wazuh vulnerability inventory from the Wazuh Indexer Read search_alerts Perform full-text search across Wazuh security alerts. Fields such as rule_description and full_log carry atta Read search_rules Search Wazuh rules by description text Read search_vulnerabilities Search Wazuh vulnerability inventory by CVE, package, agent, or description
FAQ

Questions about Wazuh

Is the Wazuh MCP server safe to use without restrictions? +

The Wazuh server is primarily read-only with 28 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Wazuh MCP server expose? +

28 tools across 1 categories: Read. 28 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Wazuh? +

Register the Wazuh MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Wazuh tool call.

Deterministic rules across all 28 Wazuh tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON WAZUH →

Instant setup, no code required.

28 Wazuh tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.