Skip to main content
Glama
Sbharadwaj05

wazuh-mcp-server

by Sbharadwaj05

wazuh_rules_info

Search and list Wazuh detection rules with filters for rule severity, compliance frameworks (PCI DSS, GDPR, HIPAA, NIST 800-53), and MITRE ATT&CK techniques to assess and refine detection coverage.

Instructions

Search and list Wazuh detection rules. Filter by rule level, compliance framework (PCI DSS, GDPR, HIPAA, NIST 800-53), or MITRE ATT&CK technique. Essential for understanding your detection coverage and tuning rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoSearch rules by name, description, or ID
levelNoFilter by rule level (0-15). Higher = more severe.
pciNoFilter by PCI DSS requirement (e.g., '10.2.5')
gdprNoFilter by GDPR article (e.g., 'Art._32')
hipaaNoFilter by HIPAA control (e.g., '164.312.b')
nist_800_53NoFilter by NIST 800-53 control (e.g., 'AU-12')
mitre_techniqueNoFilter by MITRE ATT&CK technique ID (e.g., 'T1059')
limitNoMaximum rules to return (1-500)
offsetNoPagination offset

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/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 describes the tool as a search/list operation with no side effects, but does not explicitly state read-only behavior, authentication requirements, or rate limits. The description is clear enough for a read-only query tool, but lacks explicit behavioral disclosures.

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 concise—three sentences that front-load the primary purpose, followed by filtering capabilities and utility. No extraneous words, every sentence earns its place.

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?

Given the presence of an output schema (context states 'Has output schema: true'), the tool description does not need to explain return values. It covers purpose, key parameters, and use case adequately for a search/list tool with 9 parameters. Slight deduction for missing usage guidelines.

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 input schema has 100% description coverage for all 9 parameters. The description mentions filter options but adds no semantic value beyond the schema's parameter descriptions (e.g., level range, compliance IDs). Baseline 3 is appropriate given high schema coverage.

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 explicitly states the tool's purpose: 'Search and list Wazuh detection rules.' It includes specific filtering capabilities (rule level, compliance frameworks, MITRE ATT&CK) and frames it as essential for understanding detection coverage and tuning rules, clearly differentiating from sibling tools like wazuh_rules_coverage_map.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives (e.g., wazuh_rules_coverage_map), nor does it specify prerequisites or when not to use it. It only lists features without contextual usage advice.

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