Tool Family: mitre

• Registration source: tools/mcp_tools/mitre.py:17 register_mitre_tools(mcp, *, ctx) — auto-discovered, always registered.
• Gate: @audit_tool — local-only (reads exploit_workspace/exploit_audit.jsonl filtered by target_ip, writes a JSON layer file); no target touch, no network.
• Purpose: Map an authorized-testing run's audit trail to MITRE ATT&CK techniques and write a Navigator layer JSON for blue-team handoff.

Tools Exported (1)

Signature

From tools/mcp_tools/mitre.py:23:

@mcp.tool()
@audit_tool
def export_attack_navigator(target_ip: str, output_path: str = "") -> str:

The handler reads the mitre config block and delegates to the export function in tools/mitre_export.py:269:

def export_attack_navigator(
    target_ip: str,
    output_path: str = "",
    *,
    audit_path: str | Path = "",
    technique_map_path: str | Path = "tools/mitre_technique_map.json",
    navigator_output_dir: str | Path = "reports/mitre",
    include_skills: bool = True,
) -> dict[str, Any]:

The MCP wrapper passes through only target_ip and output_path; the remaining keyword arguments come from config:

result = _export_attack_navigator(
    target_ip,
    output_path,
    technique_map_path=mitre_cfg.get("technique_map", "tools/mitre_technique_map.json"),
    navigator_output_dir=mitre_cfg.get("navigator_output_dir", "reports/mitre"),
    include_skills=bool(mitre_cfg.get("include_skill_tags", True)),
)

Inputs

Example call:

export_attack_navigator(target_ip="127.0.0.1")
export_attack_navigator(target_ip="127.0.0.1", output_path="run-127-0-0-1.json")

Output format

On success the tool returns the block built at tools/mcp_tools/mitre.py:44-50:

MITRE_NAVIGATOR_EXPORT:
layer_path: reports/mitre/<name>.json
techniques: <count>
technique_ids: T1059, T1595, ...
Open the layer JSON in ATT&CK Navigator (https://mitre-attack.github.io/attack-navigator/).

The underlying dict (per tools/mitre_export.py:278-280) is:

{
  "layer_path": "reports/mitre/run-127-0-0-1.json",
  "techniques": 2,
  "technique_ids": ["T1059", "T1595"]
}

On failure the dict carries an error key and the tool returns a single line:

BLOCKED: invalid target_ip: '...'

Failure semantics from tools/mitre_export.py:19-25:

Technique mapping

Each audit record's tool_name maps to an ATT&CK technique ID via the static map (overridable by tools/mitre_technique_map.json), with occurrence counts per technique. Built-in fallback from tools/mitre_export.py:45-61:

When include_skills is true, skill mitre_attack tags merge into the layer. Layer version is Navigator 4.5 (_NAVIGATOR_LAYER_VERSION), comments capped at 200 chars (_MAX_COMMENT_CHARS), techniques capped at 500 (_MAX_TECHNIQUES).

Dependencies

• tools/mitre_export.py — export_attack_navigator, load_technique_map, build_navigator_layer
• tools/mitre_technique_map.json — curated tool-to-technique map
• tools/skill_registry — skill ATT&CK tags (when include_skill_tags is true)
• tools/validation_utils.py — validate_target_or_ip

Config

From config.yaml:482-486:

mitre:
  enabled: true
  technique_map: tools/mitre_technique_map.json
  navigator_output_dir: reports/mitre
  include_skill_tags: true

Auditing

@audit_tool — target_ip/output_path are not secret; started/completed|blocked records mean layer exports appear in the audit trail itself.

Validation

• target_ip is not allowlist-gated (local read) but filters the audit slice; invalid values return {"error": ...} → BLOCKED: ....
• output_path traversal is coerced under navigator_output_dir.
• Audit fields are treated as data, never executed; comment length capped at 200 chars.

Tests

• tests/test_mitre_export.py — technique mapping, empty audit, skill-tag merge, output dir coercion

Related documentation

• MCP security — audit trail source
• MCP registration — decorator contract
• Terminal tool family — source of most mapped audit records

Source map

• tools/mcp_tools/mitre.py
• tools/mitre_export.py
• tools/mitre_technique_map.json
• tools/kernel/audit.py