Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_object_by_attack_id

Retrieve any MITRE ATT&CK technique, group, malware, or other object by its external ID and STIX type.

Instructions

Retrieve any MITRE ATT&CK object by its external ATT&CK ID and STIX type.

This tool supports techniques, intrusion sets (APT groups), malware,
tools, mitigations, campaigns, data sources, data components, and tactics.

Args:
    attack_id: The external ATT&CK ID (e.g., "T1055", "G0016", "S0154", "M1013").
    stix_type: The STIX object type (e.g., "attack-pattern", "intrusion-set").
    domain: ATT&CK domain ("enterprise", "mobile", or "ics").
    include_description: Whether to include the object's description field.

Returns:
    {
      "found": bool,
      "object": {
          "id": "<ATT&CK ID>",
          "name": "<object name>",
          "stix_id": "<STIX object ID>",
          "type": "<stix_type>",
          "description": "<description or null>"
      },
      "formatted": "<human-readable formatted output>",
      "message": "<status>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
attack_idYes
stix_typeYes
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 provided, so description carries the burden. It clearly indicates this is a read operation ('Retrieve') and provides the full return schema, including a 'found' flag for missing objects. It lists supported object types and explains each parameter's role. However, it does not disclose potential rate limits or authentication needs, but these are likely minimal.

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 purpose statement followed by notes, args, and returns. It is concise at about 12 lines, with no redundant sentences. The front-loading is effective. Minor improvement: could combine the supported types list into one line for even tighter prose.

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?

The description is complete for a lookup tool with 4 parameters and an output schema. It covers all parameter details, return format with fields, and lists supported object types. The output schema is clearly described, so the agent knows what to expect. No gaps for typical usage.

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?

Schema description coverage is 0%, but the description compensates fully with an 'Args:' section that explains each parameter with examples (e.g., 'T1055', 'G0016'), allowed domain values ('enterprise', 'mobile', 'ics'), and the boolean include_description. This adds meaning beyond the schema's property definitions.

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's purpose: 'Retrieve any MITRE ATT&CK object by its external ATT&CK ID and STIX type.' It lists supported object types, making the scope explicit. This distinguishes it from siblings like get_object_by_stix_id (different lookup key) or get_objects_by_type (returns list).

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. With many sibling tools (e.g., get_object_by_stix_id, get_objects_by_name), the description should mention typical use cases, but it does not. The implied usage is when you have the external ATT&CK ID and STIX type, but no exclusions or comparisons.

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