Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_techniques_detected_by_datacomponent

Identify adversary techniques detectable by a specific data component. Maps telemetry aspects to techniques attackers use to aid detection engineering.

Instructions

Get all techniques that can be detected by a specific data component.

Shows which adversary techniques can be identified by monitoring
this specific aspect of telemetry.

Args:
    datacomponent_stix_id: Data component STIX UUID identifier
                           (e.g., 'x-mitre-data-component--UUID').
    domain: ATT&CK domain ('enterprise', 'mobile', 'ics').
    include_description: Whether to include technique descriptions.

Returns:
    {
      "datacomponent": {
          "name": "<data component name or null>",
          "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": "<data source name or null>",
          "data_source_attack_id": "<data source ATT&CK ID or null>",
      } | null,

      "count": <number of techniques>,

      "techniques": [
        {
          "attack_id": "Txxxx or Txxxx.xxx" | null,
          "name": "<technique name>",
          "stix_id": "<attack-pattern--UUID>",
          "description": "<text or null>",
        },
        ...
      ],

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
include_descriptionNo
datacomponent_stix_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the burden. It includes the return format and example STIX ID, but does not disclose other behavioral aspects such as authentication requirements, rate limits, or side effects. It does not contradict any annotations (none present).

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 concise and well-structured: a brief purpose statement, a clarifying sentence, and clearly labelled Args and Returns sections. Every sentence adds value without redundancy.

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 complexity (3 parameters, detailed output schema), the description provides a complete output schema and parameter details. However, it lacks usage guidelines and some parameter constraints, making it good but not fully comprehensive for a standalone tool.

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 description provides meaning beyond the input schema by explaining each parameter in the Args section: datacomponent_stix_id with an example format, domain with default value, and include_description as a boolean. However, it does not enumerate domain options, and the coverage of schema descriptions is 0%, so the description compensates well but could be more precise.

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 action ('Get all techniques that can be detected by a specific data component') and specifies the resource (techniques detected by a data component). It distinguishes itself from siblings like 'get_datacomponents_detecting_technique' which is the reverse operation.

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 context (e.g., when you need techniques for a specific data component) but does not provide explicit guidance on when to use this tool versus alternatives like 'get_all_techniques' or 'get_techniques_by_tactic'. No when-not or exclusion conditions are given.

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