mitre-mcp

Get Techniques Mitigated by Mitigation

get_techniques_mitigated_by_mitigation

Read-onlyIdempotent

Retrieve techniques mitigated by a specific mitigation. Provide the mitigation name and domain to get a paginated list of techniques.

Instructions

Get techniques mitigated by a mitigation.

Args: ctx: FastMCP request context (injected by the server) mitigation_name: The name of the mitigation domain: Domain to query (enterprise-attack, mobile-attack, or ics-attack) limit: Maximum number of techniques to return (default: 20) offset: Index to start from when returning techniques (for pagination)

Returns: Dictionary containing the mitigation, a list of techniques and pagination metadata

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`domain`	No	enterprise-attack
`offset`	No
`mitigation_name`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mitigation`	Yes
`pagination`	Yes
`techniques`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.4.0Sep 21, 2026

addedInput schema / properties / domain / enum

Added value: +[
+  "enterprise-attack",
+  "mobile-attack",
+  "ics-attack"
+]

addedInput schema / properties / limit

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Limit"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "title": "Offset",
+  "type": "integer"
+}

addedOutput schema / $defs

Added value: +{
+  "EntityRef": {
+    "description": "Minimal id/name reference to a group or mitigation.",
+    "properties": {
+      "id": {
+        "title": "Id",
+        "type": "string"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name"
+    ],
+    "title": "EntityRef",
+    "type": "object"
+  },
+  "FormattedTechnique": {
+    "description": "Token-optimized technique object emitted by format_technique.",
+    "properties": {
+      "description": {
+        "title": "Description",
+        "type": "string"
+      },
+      "id": {
+        "title": "Id",
+        "type": "string"
+      },
+      "mitre_id": {
+        "title": "Mitre Id",
+        "type": "string"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      },
+      "type": {
+        "title": "Type",
+        "type": "string"
+      }
+    },
+    "title": "FormattedTechnique",
+    "type": "object"
+  },
+  "Pagination": {
+    "description": "Pagination metadata returned alongside paged list results.",
+    "properties": {
+      "has_more": {
+        "title": "Has More",
+        "type": "boolean"
+      },
+      "limit": {
+        "title": "Limit",
+        "type": "integer"
+      },
+      "offset": {
+        "title": "Offset",
+        "type": "integer"
+      },
+      "total": {
+        "title": "Total",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "total",
+      "offset",
+      "limit",
+      "has_more"
+    ],
+    "title": "Pagination",
+    "type": "object"
+  }
+}

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"get_techniques_mitigated_by_mitigation result."

addedOutput schema / properties

Added value: +{
+  "mitigation": {
+    "$ref": "#/$defs/EntityRef"
+  },
+  "pagination": {
+    "$ref": "#/$defs/Pagination"
+  },
+  "techniques": {
+    "items": {
+      "$ref": "#/$defs/FormattedTechnique"
+    },
+    "title": "Techniques",
+    "type": "array"
+  }
+}

addedOutput schema / required

Added value: +[
+  "mitigation",
+  "techniques",
+  "pagination"
+]

changedOutput schema / title

Previous value: -"get_techniques_mitigated_by_mitigationDictOutput"New value: +"MitigationTechniquesResult"

First observedv0.3.1May 30, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat those. It adds return-type context ('Dictionary containing the mitigation, a list of techniques and pagination metadata') and mentions pagination in the Args, which is useful. However, it doesn't disclose any additional behavioral traits such as rate limits, authentication, or what happens when no techniques are found.

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 opens with a crisp one-liner, then a structured Args list and Returns note. It is reasonably compact and well-organized. The Args section is at times tautological (e.g., 'mitigation_name: The name of the mitigation') but not excessively verbose, and the most important info is front-loaded.

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 tool has 4 parameters, one required, an output schema, and safety annotations, the description covers the return format and pagination. However, it omits usage guidelines (when to choose this tool over siblings) and lacks any example or edge-case behavior. For a read-only query tool, it is adequate but not complete.

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?

The schema has no parameter descriptions (coverage 0%), so the description must compensate. It provides some meaning for 'limit' and 'offset' (pagination semantics) and restates the enum values for 'domain', though the schema already lists them. 'mitigation_name' is merely described as 'The name of the mitigation,' adding little beyond the parameter name. Overall, partial compensation but could be more descriptive.

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?

The description states 'Get techniques mitigated by a mitigation,' which is a clear verb-resource pair and distinguishes this tool from siblings like get_techniques (all techniques) and get_techniques_by_tactic (by tactic). It is specific but doesn't explicitly contrast with alternatives; the title and one-liner are unambiguous enough.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus its siblings. The description does not mention prerequisites, filters, or scenarios where a different tool would be more appropriate. An agent must infer the use case from the name alone.

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

Deploy Server