Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_assets_targeted_by_technique

Retrieve all ICS assets targeted by a specific MITRE ATT&CK technique using its STIX ID. Identify affected components like PLCs, RTUs, and HMIs for threat analysis.

Instructions

Get all ICS assets targeted by a specific technique.

Assets represent industrial control system components such as
PLCs, RTUs, Engineering Workstations, HMIs, Control Servers, etc.

Args:
    technique_stix_id: Technique STIX UUID identifier
    domain: ATT&CK domain ('ics' strongly recommended)
    include_description: Include asset descriptions, if available

Returns:
    {
      "technique": {
          "attack_id": "Txxxx",
          "name": "...",
          "stix_id": "<attack-pattern--UUID>"
      },
      "count": int,
      "assets": [
        {
          "name": "...",
          "stix_id": "<x-mitre-asset--UUID>",
          "description": "<optional text>",
          "asset_type": "<ICS component type>",
        },
        ...
      ],
      "formatted": "<multi-line readable text>",
      "message": "<summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoics
technique_stix_idYes
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations, so description carries full burden. Provides input and output details but lacks safety or behavior notes (e.g., read-only, rate limits). Adequate but not explicit.

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 Args and Returns sections, but slightly verbose. Could tighten some explanations without losing clarity.

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 output schema exists, description fully documents return structure: technique, count, assets with fields, formatted text, and summary. Complete for the tool's complexity.

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 has 0% description coverage, so description explains all three parameters with brief, clear descriptions. Could add acceptable formats/values for technique_stix_id.

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 clearly states the tool gets all ICS assets targeted by a specific technique, distinguishing it from siblings like get_techniques_targeting_asset and get_all_assets.

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?

No explicit when-to-use or when-not-to-use guidance. Context implies it's for targeted asset retrieval, but doesn't mention alternatives like get_all_assets for broader queries.

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