Skip to main content
Glama
imouiche

MITRE ATT&CK MCP Server

by imouiche

get_all_assets

Retrieve all industrial control system (ICS) assets from the MITRE ATT&CK framework, including components like PLCs and HMIs, with options to filter deprecated entries and include descriptions.

Instructions

Get all ATT&CK assets in a domain (primarily ICS).

Assets represent industrial control system components 
(PLC, HMI, Engineering Workstation, Control Server, etc.)

Args:
    domain: ATT&CK domain ("ics" recommended)
    remove_revoked_deprecated: Exclude revoked/deprecated entries
    include_description: Include asset descriptions

Returns:
    {
      "domain": "<domain>",
      "count": <number>,
      "assets": [
        {
          "name": "...",
          "stix_id": "x-mitre-asset--UUID",
          "description": "...",
          "attack_id": "<Axxxx or None>"
        }
      ],
      "formatted": "<human-readable output>",
      "message": "<summary>"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoics
include_descriptionNo
remove_revoked_deprecatedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description must cover behavioral traits. It explains parameters and return format but omits details like rate limits, auth requirements, or side effects. The 'primarily ICS' hint is useful but incomplete for full transparency.

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?

Description is well-structured with Args and Returns sections, but slightly verbose. Could be more concise, but still efficient for a 3-param tool with output schema.

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 low complexity, presence of output schema, and clear parameter explanations, the description is complete. It covers what the tool does, how to use it, and what to expect in return.

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 description coverage is 0%, so the description compensates by explaining each parameter (domain recommendation, removing revoked, including description). The Args section adds meaningful context beyond the schema's default values.

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 it retrieves all ATT&CK assets in a domain, primarily ICS. The verb 'Get all' and resource 'assets' are specific, and it distinguishes from siblings like 'get_assets_targeted_by_technique' which is a different operation.

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 recommends 'ics' domain and clarifies the tool is for assets. While it doesn't explicitly state when not to use, the context is clear and no direct alternative exists among siblings for fetching all assets.

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