mitre-mcp

Get Techniques by Tactic

get_techniques_by_tactic

Read-onlyIdempotent

Fetch MITRE ATT&CK techniques for a specified tactic, with domain filtering, pagination, and optional exclusion of revoked or deprecated entries.

Instructions

Get techniques by tactic.

Args: ctx: FastMCP request context (injected by the server) tactic_shortname: The shortname of the tactic (e.g., 'defense-evasion') domain: Domain to query (enterprise-attack, mobile-attack, or ics-attack) remove_revoked_deprecated: Remove revoked or deprecated objects 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
`tactic_shortname`	Yes
`remove_revoked_deprecated`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`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: +{
+  "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: +"Result for tools returning a flat formatted technique list."

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_techniques_by_tacticDictOutput"New value: +"TechniquesListResult"

First observedv0.3.1May 30, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already communicate safe, idempotent, read-only behavior, so the description does not need to restate that. It adds useful context about pagination metadata and the default limit of 20, but does not go deeper into edge-case behavior like handling an unknown tactic shortname or empty results.

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 a compact, well-organized docstring with Args and Returns sections. Each parameter gets a short, meaningful explanation, there is no filler, and the core purpose is front-loaded in the first sentence.

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 moderate complexity and the presence of an output schema, the description provides everything needed to invoke it correctly: all parameter semantics, the domain choices, pagination behavior, and the return shape. No critical invocation detail appears to be missing.

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?

Schema description coverage is 0%, so the description carries the full burden of explaining all five parameters. It successfully does so: tactic_shortname is given example syntax, domain lists allowed values, remove_revoked_deprecated is explained, and limit/offset are defined as pagination controls with the default limit noted.

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 opening phrase 'Get techniques by tactic' names a specific verb, resource, and filtering dimension, and the parameter descriptions clarify exactly what tactic and domain mean. This cleanly distinguishes it from siblings like get_techniques, which returns techniques without a tactic filter, and get_technique_by_id, which targets a single technique.

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?

Usage is implied by the name and description: use it when you want techniques filtered by a tactic shortname. However, it never explicitly contrasts with sibling tools like get_techniques or get_techniques_used_by_group, so an agent is left to infer when this tool is the right choice over alternatives.

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

Deploy Server