Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_technique_tactics

Get the tactic names (kill chain phases) for a specified ATT&CK technique ID. Input the technique ID and domain to retrieve human-readable tactics.

Instructions

Get the ATT&CK tactic names associated with a given technique.

This tool:
  1) Looks up a technique by its external ATT&CK ID (e.g., "T1055").
  2) Extracts its kill chain phases (tactics) from the STIX object.
  3) Returns human-readable tactic names (e.g., "Initial Access"),
     along with the raw phase names and kill chain names.

Args:
    technique_id: External ATT&CK technique ID (e.g., "T1055", "T1055.002").
    domain: ATT&CK domain ("enterprise", "mobile", "ics").

Returns:
    {
      "found": bool,
      "technique": {
          "id": "<ATT&CK ID>",
          "name": "<technique name or null>",
          "stix_id": "<attack-pattern--... or null>",
      } | null,
      "tactics": [
        {
          "tactic": "<Human readable, e.g., 'Initial Access'>",
          "phase_name": "<raw phase name, e.g., 'initial-access'>",
          "kill_chain_name": "<kill chain name, e.g., 'mitre-attack'>"
        },
        ...
      ],
      "message": "<status message>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
technique_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description details the steps (lookup by ID, extract phases, return names) and the return format, but does not disclose behavior for edge cases (e.g., technique not found, invalid ID). With no annotations, the description carries the burden, and it partially addresses transparency but leaves gaps.

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 (brief intro, steps, Args, Returns). It is informative without being overly verbose, though it could be slightly more concise.

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 simplicity and the presence of an output schema, the description covers input parameters and return structure adequately. It includes a message field for status but does not detail error handling or performance characteristics, keeping it reasonably complete.

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?

Despite the reported 0% schema coverage, the description adds significant meaning: it specifies the format of technique_id with examples and enumerates the allowed domains. This compensates for the schema's minimal information and provides actionable guidance for parameter values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves tactic names for a given ATT&CK technique. However, it does not distinguish itself from the sibling tool 'get_tactics_by_technique', which likely serves the same purpose. Therefore, while purpose is clear, differentiation is missing.

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?

There is no guidance on when to use this tool versus alternatives like 'get_tactics_by_technique' or 'get_techniques_by_tactic'. The description lacks context for optimal usage, prerequisites, or exclusions.

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