Skip to main content
Glama
Sign In
MITRE ATT&CK MCP Server

MITRE ATT&CK MCP Server

by imouiche
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_techniques_mitigated_by_mitigation

Query techniques mitigated by a specific mitigation using its STIX ID and domain from the MITRE ATT&CK framework.

Instructions

Get all techniques mitigated by a specific mitigation (by STIX ID).

Args:
    mitigation_stix_id: STIX UUID of the mitigation (e.g., course-of-action--UUID).
    domain: ATT&CK domain ('enterprise', 'mobile', 'ics').
    include_description: Include technique descriptions in the output.

Returns:
    {
      "found": bool,
      "mitigation": {
          "attack_id": "...",
          "name": "...",
          "stix_id": "course-of-action--..."
      } | null,
      "count": int,
      "techniques": [
          {
              "attack_id": "Txxxx",
              "name": "...",
              "stix_id": "...",
              "description": "...",
          },
          ...
      ],
      "formatted": "<multi-line text>",
      "message": "<summary>"
    }

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": {
      "mitigation_stix_id": "<mitigation_stix_id>"
    },
    "name": "get_techniques_mitigated_by_mitigation"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoenterprise
mitigation_stix_idYes
include_descriptionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses the return structure including fields like 'found', 'mitigation', 'count', 'techniques', 'formatted', and 'message'. It does not mention error handling, rate limits, or pagination, but for a simple query tool the behavioral information is adequate.

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

Conciseness4/5

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

The description is concise with a brief one-sentence purpose followed by structured Args and Returns sections. It is front-loaded and contains no redundant information, though the Python docstring format could be slightly more compact.

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 tool's complexity (3 parameters, required output schema present), the description is complete. It covers input details, output structure, and examples. There are no missing elements for an agent to invoke the tool correctly.

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

Parameters5/5

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

The schema description coverage is 0%, but the description compensates by explaining each parameter: mitigation_stix_id (STIX UUID format), domain (with explicit examples 'enterprise', 'mobile', 'ics'), and include_description (boolean). This adds significant meaning beyond the schema alone.

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 states the action: 'Get all techniques mitigated by a specific mitigation (by STIX ID).' It uses a specific verb ('Get') and resource ('techniques mitigated by mitigation'), and the name distinguishes it from the sibling tool 'get_mitigations_mitigating_technique' which does the reverse.

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 does not explicitly state when to use this tool versus alternatives. The usage is implied by the name and parameters, but there is no direct guidance on when-not-to-use or alternatives like 'get_mitigations_mitigating_technique'.

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

Deploy Server

Other Tools