mcp-server-wazuh

Search Vulnerabilities

search_vulnerabilities

Read-onlyIdempotent

Search Wazuh vulnerability state detections newest first, using OpenSearch query strings and optional agent ID filters to identify affected agents.

Instructions

Search the wazuh-states-vulnerabilities index, newest detections first. Example query: vulnerability.severity:Critical

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_vulnerabilities"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size, from 1 to 100
`query`	No	OpenSearch query_string. Empty matches the vulnerability state index.
`offset`	No	Result offset, from 0 to 10000
`agent_id`	No	Optional agent id filter

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the non-obvious detail that results are returned newest-first, which is genuinely useful, but it says nothing about pagination depth, result volume, or the openWorld nature of the free-form query.

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 compact sentences with the core purpose and ordering front-loaded, followed by a directly usable example. Nothing is redundant and no sentence needs to be re-read.

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?

An output schema exists so return values need no explanation, and all four parameters are fully documented in the schema. The remaining gap is routing guidance against the sibling search tools, which matters given how similar search_vulnerabilities, search_findings and search_events sound.

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 coverage is 100%, so every parameter (limit, query, offset, agent_id) is already described in the schema, establishing the baseline of 3. The example 'vulnerability.severity:Critical' illustrates the field-path convention for the free-form query_string parameter, which is a modest but real addition beyond the schema.

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?

States a specific verb and resource ('Search the wazuh-states-vulnerabilities index') plus a result ordering ('newest detections first'), which pins down both scope and sort behavior. It does not explicitly contrast itself with search_findings or search_events, so sibling differentiation relies on the index name alone.

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?

The index name implies the use case (vulnerability detections), and the sample query hints at the intended filtering style, but there is no explicit statement of when to prefer this over search_findings or search_events, and no prerequisites or exclusions are given.

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

Deploy Server