Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_procedure_examples_by_tactic

Retrieve real-world procedure examples of threat actors using techniques under a specific MITRE ATT&CK tactic. Shows how groups execute tactics like Initial Access or Persistence.

Instructions

Get all procedure examples for techniques in a specific tactic.

Shows real-world examples of how threat groups use techniques that fall
under a given tactic (e.g., Initial Access, Persistence).

Args:
    tactic: Tactic name (e.g., "Initial Access", "Persistence").
            Case-insensitive; should match ATT&CK tactic names.
    domain: ATT&CK domain ('enterprise', 'mobile', 'ics').
    include_description: Include example descriptions when available.

Returns:
    {
      "tactic": {
          "name": "<tactic name>",
          "attack_id": "TAxxxx" | null,
          "stix_id": "x-mitre-tactic--UUID" | null,
      },
      "count": int,
      "examples": [
        {
          "relationship_id": "relationship--UUID",
          "description": "<procedure text or null>",
          "group": {
            "attack_id": "Gxxxx" | null,
            "name": "<group name or null>",
            "stix_id": "intrusion-set--UUID" | null,
          },
          "technique": {
            "attack_id": "Txxxx or Txxxx.xxx" | null,
            "name": "<technique name or null>",
            "stix_id": "attack-pattern--UUID" | null,
          },
        },
        ...
      ],
      "formatted": "<multi-line human-readable text>",
      "message": "<summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
tacticYes
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description discloses it's a read operation via 'Get all procedure examples'. It details the return format and parameters, though it could explicitly state no side effects or idempotency.

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 yet comprehensive, with clear sections for args and returns. Every sentence serves a purpose, and the bullet format aids readability.

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?

Given the presence of an output schema, the description covers all necessary aspects: purpose, parameters with defaults, and return structure. It is complete for an AI agent to select and invoke correctly.

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?

Schema coverage is 0%, but the description provides semantics for each parameter: case-insensitivity for tactic, default for domain, boolean for include_description. This adds value beyond the schema's type info.

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 it retrieves procedure examples for techniques within a specific tactic, using the verb 'Get' and identifying the resource. It distinguishes itself from siblings like get_procedure_examples_by_technique by focusing on a tactic vs. a single technique.

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

Usage Guidelines4/5

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

The description explains when to use this tool (for examples grouped by tactic) and implies it's for ATT&CK data. It does not explicitly mention when not to use or name alternatives, but the sibling list provides context.

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