Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_group_techniques

Retrieve all MITRE ATT&CK techniques used by a specified threat group by name or alias, including relationships and descriptions. Supports enterprise, mobile, and ICS domains.

Instructions

Get all techniques used by a specific APT group (intrusion set).

This tool:
  1) Locates a group by name or alias (case-insensitive, partial match).
  2) Uses MITRE's get_techniques_used_by_group() to retrieve techniques
     related to that group (via 'uses' relationships).

Args:
    group_name: Group name or alias (e.g., "APT29", "Lazarus Group").
    domain: ATT&CK domain ("enterprise", "mobile", or "ics").
    include_description: Whether to include descriptions in the output.

Returns:
    {
      "found": bool,  # whether the group was found
      "group": {
          "attack_id": "GXXXX",
          "name": "...",
          "aliases": [...],
          "stix_id": "intrusion-set--...",
          "description": "..." | null
      } | null,
      "count": <number of techniques>,
      "techniques": [
        {
          "attack_id": "TXXXX or TXXXX.YYY",
          "name": "...",
          "stix_id": "attack-pattern--...",
          "description": "..." | null,
          "relationships": [
            {
              "stix_id": "relationship--...",
              "relationship_type": "uses",
              "description": "..." | null,
              "source_ref": "...",
              "target_ref": "..."
            },
            ...
          ]
        },
        ...
      ],
      "formatted": "<human-readable technique list>",
      "message": "<status summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
group_nameYes
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so the description carries the full burden. It discloses the lookup process, partial matching, and output structure. However, it does not explicitly state that the operation is read-only or has no side effects, which is minor given the clear intent.

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 well-structured with clear sections for purpose, steps, args, and output. It is somewhat lengthy but each part serves a purpose. Minor redundancy in args list versus schema.

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 presence of an output schema, the description adequately covers return values. It lacks details on error handling (e.g., group not found) but the output includes a 'found' boolean. Overall, it is sufficiently complete for a retrieval tool.

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 fully explains all three parameters, their defaults, and the group_name lookup semantics. This adds essential meaning beyond the schema's property titles.

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?

Description clearly states the tool retrieves all techniques used by a specific APT group, with matching details (case-insensitive, partial). This distinguishes it from siblings like get_software_used_by_group or get_groups_using_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?

The description implies usage for group techniques but does not explicitly guide when to choose this over alternatives. No exclusions or comparisons to sibling tools are provided, leaving the agent to infer context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/imouiche/complete-mitre-attack-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server