wazuh-mcp

Query the MITRE ATT&CK catalogue

wazuh_mitre

Read-onlyIdempotent

Look up MITRE ATT&CK techniques, tactics, groups, software, or mitigations from the manager's catalogue. Expand a technique ID from an alert into its description, tactics, and mitigations.

Instructions

Look up MITRE ATT&CK techniques, tactics, groups, software or mitigations from the manager's bundled catalogue. Use it to expand a technique ID seen in an alert into its description, tactics and mitigations.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Specific IDs. Accepts the familiar ATT&CK numbers — ['T1110'] for techniques, ['TA0006'] for tactics, ['G0001'] for groups — as well as internal STIX ids like ['attack-pattern--0042a9f5-f053-4769-b3ef-9ad018dfa298'].
`limit`	No
`offset`	No
`search`	No	Free-text search across names and descriptions.
`resource`	No	Which part of the ATT&CK catalogue to query.	techniques

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.5/5.0

Behavior4/5

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

The annotations already declare the operation as read-only, idempotent, and non-destructive, and the description is consistent with that behavior. No side effects are implied, so no additional disclosure is needed.

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 compact and immediately informative, with no redundant wording or irrelevant detail. It front-loads the core purpose and then adds the primary usage scenario.

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 modest parameter set and the presence of an output schema, the description provides sufficient context for correct invocation. It specifies the data source, supported resource types, and a concrete real-world trigger for using the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides helpful descriptions for ids, search, and resource, including concrete examples of accepted ID formats. Limit and offset are not described but are standard pagination parameters whose meaning is evident from their names and defaults.

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 clearly identifies the tool as a lookup operation against the MITRE ATT&CK catalogue, listing the exact resource types it covers. It is easily distinguished from all sibling tools, none of which target MITRE data.

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 an explicit use case: expanding a technique ID seen in an alert into its description, tactics, and mitigations. It does not name alternative tools, but the scenario is clear enough to guide selection.

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