Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_techniques_targeting_asset

Identify adversary techniques from MITRE ATT&CK that target a given ICS asset, enabling threat assessment for industrial control systems.

Instructions

Get all techniques that target a specific ICS asset.

Shows which adversary techniques can affect a given industrial
control system component.

Args:
    asset_stix_id: STIX ID of the ICS asset
    domain: Domain (default: 'ics')
    include_description: Whether to include descriptions in formatted output

Returns:
    {
        "found": bool,
        "count": int,
        "techniques": [
            {
                "id": "<ATT&CK ID>",
                "name": "...",
                "stix_id": "...",
                "description": "..." | None
            },
            ...
        ],
        "formatted": "<optional pretty text>",
        "message": "..."
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoics
asset_stix_idYes
include_descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as idempotency, data freshness, authentication requirements, or side effects. The verb 'get' implies read-only, but this is not explicitly stated. The return format is described but that is expected.

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 short summary, an Args section, and a Returns section. It is concise without unnecessary detail, though the Returns section could be more integrated.

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 presence of an output schema in the description and the existence of sibling tools, the description is largely complete. It lacks guidance on when to use this tool over its reverse counterpart, but the core functionality and return structure are well covered.

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?

The description adds meaningful information beyond the schema for all three parameters: it explains 'asset_stix_id' as the STIX ID of the ICS asset, 'domain' with default 'ics', and 'include_description' as whether to include descriptions. This compensates for the schema's minimal titles.

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 'Get all techniques that target a specific ICS asset' and elaborates with 'Shows which adversary techniques can affect a given industrial control system component.' This specific verb-resource combination distinguishes it from sibling tools like 'get_assets_targeted_by_technique' and 'get_all_techniques'.

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?

The description implies usage by stating the function, but does not explicitly contrast with siblings like the reverse tool 'get_assets_targeted_by_technique' or provide when-not-to-use context. The presence of siblings in the list does not compensate for lack of explicit guidance.

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