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_attributing_to_campaign

Retrieve all APT groups attributed to a given campaign. Input a campaign STIX ID to get group names, aliases, and relationships.

Instructions

Get all APT groups (intrusion sets) attributed to a specific campaign.

This is a reverse lookup: Campaign → Groups.
It follows attribution relationships from a campaign STIX ID to
intrusion sets (groups).

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

Returns:
    {
      "campaign": {
          "attack_id": "CXXXX" | null,
          "name": "<campaign name or null>",
          "stix_id": "<campaign--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": "<type>",
              "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": {
      "campaign_stix_id": "<campaign_stix_id>"
    },
    "name": "get_groups_attributing_to_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoenterprise
campaign_stix_idYes
include_descriptionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return structure in detail and explains arguments, but it does not mention any behavioral traits such as idempotency, error handling, permissions, or rate limits. For a read-only get operation, this is adequate but not exceptional.

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: a clear one-sentence purpose, a brief explanation, then separate 'Args' and 'Returns' sections. While the return block is long, it is necessary due to the absence of a separate output schema. No superfluous text.

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 tool's moderate complexity (3 parameters, no enums, no formal output schema), the description covers purpose, all parameters, and the full return structure. It lacks notes on error conditions or edge cases (e.g., invalid STIX ID), but for a straightforward lookup tool, it is largely complete.

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, yet the description provides an 'Args' section that explains each parameter (campaign_stix_id, domain with allowed values, include_description) and their defaults. This adds significant meaning beyond the raw schema, compensating for the lack of schema descriptions. Baseline for 3 parameters is 3, but the description elevates it to 4.

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 clearly states the tool retrieves APT groups attributed to a specific campaign, explicitly labels it as a 'reverse lookup: Campaign → Groups', and distinguishes it from sibling tools like get_campaigns_attributed_to_group (the opposite direction). The verb 'Get' and resource 'APT groups' are specific.

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 when to use it (when you have a campaign STIX ID and want groups) via the 'reverse lookup' phrasing, but it does not explicitly state when not to use it or name alternative tools for other scenarios (e.g., get_groups_using_software for software-based lookups).

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