mitre-mcp

Get Techniques Used by Group

get_techniques_used_by_group

Read-onlyIdempotent

Retrieve the techniques used by a threat group from MITRE ATT&CK. Specify group name and domain to get a paginated list of techniques.

Instructions

Get techniques used by a group.

Args: ctx: FastMCP request context (injected by the server) group_name: The name of the group 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 group, a list of techniques and pagination metadata

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`group`	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_used_by_group result."

addedOutput schema / properties

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

addedOutput schema / required

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

changedOutput schema / title

Previous value: -"get_techniques_used_by_groupDictOutput"New value: +"GroupTechniquesResult"

First observedv0.3.1May 30, 2026

TDQS

A3.9/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 safety profile is clear. The description adds mildly useful behavioral context by stating the return shape (group, list of techniques, pagination metadata) and describing pagination via limit/offset. It does not go deeper into edge cases such as unknown group names or empty results, but that gap is minor given 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 description is a well-organized docstring with an opening summary followed by concise Args and Returns sections. Every parameter earns its place and there is no redundant prose. The formatting is slightly heavier than necessary, but it remains readable and efficient.

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?

For a read-only lookup tool, the description covers the essential invocation details: required group_name, optional domain, and pagination controls. The output schema and annotations take care of return structure and safety behaviorgrave. The only material omission is usage guidance relative to sibling tools, which is handled by the tool name but not described explicitly.

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

Parameters4/5

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

The input schema has 0% description coverage, and the description compensates by explaining each parameter: group_name as the group to query, domain with its allowed values, limit as the maximum number of techniques, and offset as the pagination starting index. This adds meaning that is absent from the schema's bare properties. It could be improved by noting expected types, but the schema already provides types and defaults.

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 starts with a clear verb and resource: 'Get techniques used by a group.' This directly distinguishes the tool from siblings like get_techniques and get_techniques_by_tactic by specifying the grouping dimension. The title reinforces the purpose without ambiguity.

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 usage is implied: use this tool when you need techniques associated with a specific group. However, it provides no explicit guidance on when not to use it or when to prefer a sibling tool such as get_techniques_by_tactic or get_techniques. The description defines what the tool does but does not give selection criteria.

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

Deploy Server