Skip to main content
Glama
Sbharadwaj05

wazuh-mcp-server

by Sbharadwaj05

wazuh_list_alerts

Query Wazuh security alerts using filters like agent ID, rule level, MITRE technique, or free-text search. Enables incident triage, threat hunting, and security event overview.

Instructions

Query Wazuh security alerts with powerful filters. Use this to triage incidents, hunt for specific threat patterns, or get an overview of recent security events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idNoFilter alerts to a specific agent ID (e.g., '001')
agents_listNoComma-separated agent IDs to filter (e.g., '001,002,003')
min_levelNoMinimum rule level (3-15). Higher = more severe. Use 12+ for critical only.
rule_idNoFilter by a specific Wazuh rule ID (e.g., '5710' for SSH brute force)
rule_idsNoComma-separated rule IDs (e.g., '5710,5712,5760')
mitre_idNoFilter by MITRE ATT&CK technique ID (e.g., 'T1110' for brute force)
searchNoFree-text search across alert fields (IP, hostname, command, etc.)
sortNoSort field, prefix with '-' for descending (e.g., '-timestamp')
limitNoMaximum number of alerts to return (1-500)
offsetNoPagination offset for scrolling through results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the tool is read-only, what the response format looks like, or any side effects. The name implies a read operation, but explicit statements about behavior are missing.

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?

Two sentences with no redundancy. The first sentence states the core purpose, and the second lists use cases. Every word earns its place.

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

Completeness3/5

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

Given the tool has 10 optional parameters and an output schema exists, the description is brief but adequate. It could mention pagination defaults or output structure, but the parameter schema covers details, and the output schema likely clarifies return values.

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?

Schema description coverage is 100%, so the schema already explains each parameter. The description adds value by framing the tool's purpose but does not provide additional semantic meaning beyond the schema. Baseline 3 applies.

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

Purpose4/5

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

The description uses a clear verb 'Query' and resource 'Wazuh security alerts', and provides specific use cases (triage, hunt, overview). While it doesn't explicitly differentiate from siblings like wazuh_get_alert or wazuh_alert_summary, the use cases imply a general listing/filtering role.

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?

The description gives concrete scenarios for using this tool: triaging incidents, hunting for threat patterns, or getting an overview. However, it does not mention when to avoid using it or suggest alternative tools for single-alert retrieval or summaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sbharadwaj05/wazuh-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server