Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_mitigations_mitigating_technique

Retrieve all mitigations that address a specific MITRE ATT&CK technique, enabling identification of defensive measures for threat intelligence and security workflows.

Instructions

Get all mitigations that address a specific technique.

Helper returns: list[RelationshipEntry[Mitigation]]
So each item is a wrapper that contains a Mitigation object (usually in `.object`).
We must unwrap before extracting fields.

Returns (same schema as before):
  {
    "found": bool,
    "technique": {...} | null,
    "count": int,
    "mitigations": [...],
    "formatted": str,
    "message": str
  }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
technique_stix_idYes
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description must disclose behavior. It explains that the helper returns a list of RelationshipEntry[Mitigation] requiring unwrapping, and provides the full response schema. This is sufficient for a read-only query with no side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is 7 lines, includes a somewhat technical reference to 'list[RelationshipEntry[Mitigation]]', and could be more concise. However, it is front-loaded with the primary purpose and uses clear language.

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

Completeness3/5

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

Given the output schema is provided, the description's inclusion of the return structure adds value but does not compensate for missing parameter descriptions. The tool is simple (read-only, few parameters), so completeness is adequate but not exemplary.

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

Parameters2/5

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

Schema coverage of parameters is 0%—the description adds no information about 'technique_stix_id', 'domain', or 'include_description' beyond their names and defaults. The description does not clarify expected formats, constraints, or usage patterns for these 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?

Description explicitly states 'Get all mitigations that address a specific technique', providing a clear verb (Get), resource (mitigations), and scope (for a specific technique). This distinguishes it from siblings like 'get_all_mitigations' (all mitigations) and 'get_techniques_mitigated_by_mitigation' (reverse mapping).

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 description implies usage for a specific technique but provides no when-to-use or when-not-to-use guidance, nor does it reference alternative tools from the sibling list. The context is implied but not explicitly stated.

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/imouiche/complete-mitre-attack-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server