Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_software_using_technique

Find software (malware/tools) that leverage a specific MITRE ATT&CK technique via reverse lookup from technique STIX ID.

Instructions

Get all software (malware/tools) that use a specific technique.

This is a reverse lookup: Technique → Software.
It follows 'uses' relationships from a technique STIX ID to software
(malware and tools) that implement or leverage that technique.

Args:
    technique_stix_id: STIX ID of the technique
                       (e.g., "attack-pattern--UUID").
    domain: ATT&CK domain ("enterprise", "mobile", "ics").
    include_description: Whether to include software descriptions.

Returns:
    {
      "technique": {
          "attack_id": "TXXXX or TXXXX.YYY" | null,
          "name": "<technique name or null>",
          "stix_id": "<attack-pattern--UUID>",
          "description": "<text or null>",
      } | null,

      "count": <number of software objects>,

      "software": [
        {
          "attack_id": "SXXXX or similar" | null,
          "name": "<software name>",
          "stix_id": "<software STIX ID>",
          "type": "<malware|tool|...>",
          "description": "<text or null>",
          "relationships": [
            {
              "stix_id": "<relationship--UUID>",
              "relationship_type": "uses",
              "description": "<relationship description or null>",
              "source_ref": "<source STIX ID>",
              "target_ref": "<target STIX ID>",
            },
            ...
          ]
        },
        ...
      ],

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoenterprise
technique_stix_idYes
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, description provides full behavioral disclosure of output structure including relationships array. It does not mention safety or performance, but as a read query, the detailed return format is adequate.

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?

Well-structured with clear Args and Returns sections. First sentence is front-loaded. Slightly long due to detailed output example, but every sentence adds value.

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?

Complete for the tool's complexity: covers purpose, all parameters, and full return structure. Even provides an example output, which compensates for no output schema in metadata.

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 0% schema coverage, description explains all three parameters (technique_stix_id, domain with allowed values, include_description) with types and examples, adding meaning beyond schema.

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?

Description starts with clear statement: 'Get all software (malware/tools) that use a specific technique.' It specifies reverse lookup and direction, distinguishing from siblings like get_techniques_used_by_software.

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?

Description explicitly states technique-to-software direction and that it follows 'uses' relationships. While no explicit when-not-to-use or alternatives, the context is clear and the sibling list shows differentiated tools.

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