wazuh-mcp

SCA checks within a policy

wazuh_sca_checks

Read-onlyIdempotent

Retrieve SCA policy checks for a Wazuh agent, including remediation text. Filter by result like 'failed' to focus on actionable hardening steps.

Instructions

List the individual configuration checks in one SCA policy, including the remediation text for each. Filter to result='failed' to get an actionable hardening list for a host.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`result`	No	Filter by outcome. 'failed' is the actionable set.	failed
`search`	No	Free-text match across check titles and text.
`agent_id`	Yes	Agent ID, e.g. '001'.
`policy_id`	Yes	Policy ID from wazuh_sca_policies, e.g. 'cis_debian10' or 'cis_win2019_enterprise'.
`include_remediation`	No	Include rationale and remediation prose. Informative but verbose; turn off when you only need the list of failures.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds no additional behavioral details (e.g., pagination, rate limits), but also does not contradict the annotations. Given the annotations cover the key behavioral traits, a neutral score is appropriate.

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 two sentences, direct, and free of redundant wording. It packs the core purpose and a key usage hint without unnecessary elaboration.

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

Completeness5/5

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

Given the rich schema (with per-parameter descriptions) and complete annotations, the description sufficiently explains what the tool does and how to use it for a common scenario. No critical missing information prevents correct invocation.

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 covers 71% of parameters with descriptions, and the tool description reinforces the meaning of 'result' and 'include_remediation' but does not add substantial new insight beyond what the schema already provides. The description does not clarify the undocumented 'limit' and 'offset' parameters.

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 uses a clear verb ('List'), specifies the resource ('individual configuration checks in one SCA policy'), and includes distinctive details like remediation text and the actionable filter. It clearly distinguishes this tool from wazuh_sca_policies which lists policies themselves.

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?

Provides actionable guidance by suggesting filtering with result='failed' to get a hardening list. This is a concrete usage tip, though it does not explicitly contrast with sibling tools or state when not to use it.

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