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

MITRE ATT&CK MCP Server

by imouiche
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_all_datacomponents

Get all ATT&CK data components for a specified domain, with options to exclude revoked or deprecated entries and include detailed descriptions.

Instructions

Get all ATT&CK data components in a domain.

Data components are specific aspects of a data source that can be monitored.
For example, the "Process" data source has components like
"Process Creation", "Process Termination", etc.

Args:
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    remove_revoked_deprecated: Whether to exclude revoked/deprecated entries.
    include_description: Whether to include descriptions.

Returns:
    {
      "domain": "<domain>",
      "count": <number of data components>,
      "datacomponents": [
        {
          "name": "<data component name>",
          "stix_id": "<x-mitre-data-component--UUID>",
          "description": "<text or null>",
          "data_source_stix_id": "<x-mitre-data-source--UUID or null>",
          "data_source_name": "<parent data source name or null>",
          "data_source_attack_id": "<data source ATT&CK ID or null>"
        },
        ...
      ],
      "formatted": "<optional human-readable output>",
      "message": "<summary>"
    }

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_all_datacomponents"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoenterprise
include_descriptionNo
remove_revoked_deprecatedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It describes a read operation with no side effects, and it details the return format extensively, including fields like stix_id and data_source_name. No hidden behaviors are indicated.

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 a summary, example explanation, Args, and Returns sections. It is moderately sized; the example of 'Process' could be slightly shorter but is still helpful.

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?

The description fully specifies the output schema and parameter defaults. It covers the core use case well, though it could mention relationships to sibling tools like get_datacomponents_detecting_technique for better context.

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?

Although schema description coverage is 0%, the description includes an Args section that explains each parameter (domain, remove_revoked_deprecated, include_description). This adds meaning beyond the raw schema, specifying defaults and the purpose of each parameter.

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 'Get all ATT&CK data components in a domain' and explains what data components are with an example. It distinguishes this tool from siblings like get_all_datasources and get_all_techniques by focusing specifically on data components.

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 retrieving all data components in a domain but does not provide explicit guidance on when to use this tool versus alternatives like get_datacomponents_detecting_technique. No when-not-to-use or exclusions are mentioned.

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