mitre-mcp

Get Groups

get_groups

Read-onlyIdempotent

Retrieve threat actor groups from MITRE ATT&CK for a chosen domain, filter out revoked or deprecated entries, and paginate through results with limit and offset.

Instructions

Get groups 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) remove_revoked_deprecated: Remove revoked or deprecated objects limit: Maximum number of groups to return (default: 20) offset: Index to start from when returning groups (for pagination)

Returns: Dictionary containing a list of groups and pagination metadata

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`groups`	Yes
`pagination`	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: +{
+  "GroupResult": {
+    "description": "Single group entry in get_groups results.",
+    "properties": {
+      "aliases": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Aliases",
+        "type": "array"
+      },
+      "description": {
+        "title": "Description",
+        "type": "string"
+      },
+      "id": {
+        "title": "Id",
+        "type": "string"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "description",
+      "aliases"
+    ],
+    "title": "GroupResult",
+    "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_groups result."
```

addedOutput schema / properties

Added value: +{
+  "groups": {
+    "items": {
+      "$ref": "#/$defs/GroupResult"
+    },
+    "title": "Groups",
+    "type": "array"
+  },
+  "pagination": {
+    "$ref": "#/$defs/Pagination"
+  }
+}

addedOutput schema / required

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

changedOutput schema / title

Previous value: -"get_groupsDictOutput"New value: +"GroupsResult"

First observedv0.3.1May 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds context by noting 'token-optimized responses' and specifying that the return is a dictionary with a list of groups and pagination metadata, going beyond the annotation baseline.

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 front-loaded with its primary purpose and then uses a compact Args/Returns list. Every sentence contributes information, and there is no filler or redundant repetition of schema fields without added value.

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?

This is a straightforward retrieval operation with an output schema and clear annotations. The description covers all parameters, pagination behavior, and the return shape, so an agent has everything needed to call it correctly without further research.

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 fully compensates. The Args section explains every schema parameter: domain enum values, remove_revoked_deprecated semantics, limit's default and purpose, and offset's pagination role, adding far more meaning than the bare schema.

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 opens with 'Get groups from the MITRE ATT&CK framework', specifying a precise verb and resource. The word 'groups' distinguishes it from sibling tools like get_techniques and get_tactics, and the added 'token-optimized responses' further clarifies its purpose.

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 tool is for retrieving ATT&CK groups but never explicitly contrasts it with sibling tools or states when not to use it. There is no alternative routing such as 'for techniques, see get_techniques', so usage guidance is left to inference.

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

Deploy Server