Skip to main content
Glama
Sign In
MITRE ATT&CK MCP Server

MITRE ATT&CK MCP Server

by imouiche
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_groups_using_technique

Retrieve all APT groups associated with a specific MITRE ATT&CK technique. Reverse lookup from technique to groups using STIX IDs.

Instructions

Get all APT groups (intrusion sets) that use a specific technique.

This is a reverse lookup: Technique → Groups.
It follows 'uses' relationships from a technique STIX ID to intrusion sets.

Args:
    technique_stix_id: STIX ID of the technique
                       (e.g., "attack-pattern--UUID").
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    include_description: Whether to include group descriptions.

Returns:
    {
      "technique": {
          "attack_id": "TXXXX or TXXXX.YYY" | null,
          "name": "<technique name or null>",
          "stix_id": "<attack-pattern--UUID>",
          "description": "<text or null>",
      } | null,

      "count": <number of groups>,

      "groups": [
        {
          "attack_id": "GXXXX" | null,
          "name": "<group name>",
          "aliases": [...],
          "stix_id": "<intrusion-set--UUID>",
          "description": "<text or null>",
          "relationships": [
            {
              "stix_id": "<relationship--UUID>",
              "relationship_type": "uses",
              "description": "<relationship description or null>",
              "source_ref": "<source STIX ID>",
              "target_ref": "<target STIX ID>",
            },
            ...
          ]
        },
        ...
      ],

      "formatted": "<human-readable list of groups>",
      "message": "<status summary>"
    }

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "technique_stix_id": "<technique_stix_id>"
    },
    "name": "get_groups_using_technique"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoenterprise
technique_stix_idYes
include_descriptionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It details the relationship traversal ('follows uses relationships from a technique STIX ID to intrusion sets') and provides an exhaustive return schema. It does not disclose potential side effects or permissions, but the operation is inherently read-only.

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 fairly long due to the included return schema, but it is well-structured: brief intro, Args list, and Returns section. It is front-loaded with purpose. A minor reduction could be made, but it remains efficient.

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?

Despite the output schema being provided, the description still covers the return structure. All three input parameters are described. For a reverse lookup tool with moderate complexity, the description is fully adequate.

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?

Schema description coverage is 0%, so the description must compensate. The Args section explains each parameter: technique_stix_id with format example, domain with valid values, and include_description with semantics. This adds substantial meaning beyond 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 starts with a clear verb-resource phrase: 'Get all APT groups (intrusion sets) that use a specific technique.' It further distinguishes itself as a reverse lookup ('Technique → Groups'), differentiating it from sibling tools like get_techniques_used_by_group.

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

Usage Guidelines4/5

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

The description explicitly states this is a reverse lookup and follows 'uses' relationships, implying when to use it. Sibling tools include get_techniques_used_by_group (the forward direction), providing implicit differentiation. However, it lacks explicit when-not-to-use or alternative tool instructions.

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

Deploy Server

Other Tools