mitre-mcp

Get Techniques

get_techniques

Read-onlyIdempotent

Retrieve MITRE ATT&CK techniques with filters for domain, subtechniques, and descriptions. Supports pagination to manage large result sets.

Instructions

Get techniques from the MITRE ATT&CK framework with token-optimized responses.

Args: ctx: FastMCP request context (injected by the server) domain: Domain to query (enterprise-attack, mobile-attack, or ics-attack) include_subtechniques: Include subtechniques in the result remove_revoked_deprecated: Remove revoked or deprecated objects include_descriptions: Whether to include technique descriptions (uses more tokens) limit: Maximum number of techniques to return (default: 20) offset: Index to start from when returning techniques (for pagination)

Returns: Dictionary containing a list of techniques and pagination metadata

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`domain`	No	enterprise-attack
`offset`	No
`include_descriptions`	No
`include_subtechniques`	No
`remove_revoked_deprecated`	No

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.4.0Sep 21, 2026

addedInput schema / properties / domain / enum

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

addedOutput schema / $defs

Added value: +{
+  "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 result: paged technique list plus pagination metadata."

addedOutput schema / properties

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

addedOutput schema / required

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

changedOutput schema / title

Previous value: -"get_techniquesDictOutput"New value: +"TechniquesPageResult"

First observedv0.3.1May 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond that: responses are token-optimized, including descriptions consumes more tokens, and the return value contains pagination metadata. There is no contradiction with the annotations.

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 lead sentence is concise and the parameter bullets are compact and informative. It is longer than strictly necessary, and 'token-optimized responses' is somewhat vague, but each line earns its place by explaining a parameter or the return shape.

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

Completeness4/5

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

Given the 6 parameters, annotations, and output schema, the description covers the invocation essentials: all arguments are explained, pagination is described, and the return is summarized. The main missing piece is explicit routing among the sibling tools, but that gap is also captured in usage_guidelines.

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?

With 0% schema description coverage, the description carries the whole burden and succeeds by explaining every parameter—domain values, default 20 limit, offset pagination, subtechnique inclusion, revoked/deprecated filtering, and the token cost of descriptions. This adds meaning beyond the bare names, types, and defaults in the schema.

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 names a specific operation and resource: it retrieves techniques from the MITRE ATT&CK framework, and the parameter list clarifies scope by domain and subtechniques. However, it never states whether this is the unfiltered/general listing as opposed to the filtered sibling tools such as get_techniques_by_tactic, get_techniques_used_by_group, or get_technique_by_id, so it is clear but not fully differentiating.

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 this is a general technique-fetching tool through its broad name and pagination/filtering parameters, but it gives no explicit when-to-use or when-not-to-use guidance and does not mention any sibling tools. An agent has to infer that get_techniques_by_tactic or get_technique_by_id would be better choices for narrower lookups.

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

Deploy Server