wazuh-mcp

search_rules

Search Wazuh detection rules by matching rule description text. Filter by minimum severity level and control pagination.

Instructions

Search Wazuh rules by description text

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "description": "<description>"
    },
    "name": "search_rules"
  }
}

Input Schema

Name	Required	Description
`level`	No	Minimum severity level filter
`limit`	No	Maximum number of items to return (1-100)
`offset`	No	Pagination offset
`description`	Yes	Search term to match against rule descriptions

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.1.0Jun 23, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / properties / description / maxLength
```
Added value: +256
```
- addedInput schema / properties / description / minLength
```
Added value: +1
```
- addedInput schema / properties / description / pattern
```
Added value: +"^[\\p{L}\\p{N}\\s._:@/+,\\-#()[\\]]+$"
```
- changedInput schema / properties / limit / description
```
Previous value: -"Maximum number of rules to return (1-100)"New value: +"Maximum number of items to return (1-100)"
```
- changedInput schema / properties / offset / maximum
```
Previous value: -9007199254740991New value: +100000
```
Changed3 schema fields changedMay 6, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / level / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
First observedv1.0.0Feb 7, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden for behavioral transparency. It doesn't mention read-only nature, case sensitivity, or partial results. The brief description adds minimal behavioral context.

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?

One short, direct sentence with no wasted words. Information is front-loaded and necessary.

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

Completeness2/5

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

Given no output schema, no annotations, and 4 parameters, the description is too minimal. It doesn't explain the return format (list of rule objects), pagination behavior, or filtering nuances beyond what the schema provides.

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%; all parameters have descriptions in the schema. The tool description adds no additional meaning beyond 'by description text', so baseline 3 applies.

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 'Search Wazuh rules by description text' clearly states the verb (search), resource (Wazuh rules), and method (by description text). It distinguishes from siblings like list_rules (lists all) and get_rule (by ID).

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., list_rules, get_rule). Implies usage from the action 'search' but lacks when-not scenarios or sibling comparisons.

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