Threat Modeling MCP Server

Overview Schema Source Related Servers Discussions Admin

export_threat_model

Exports strict Threat Composer JSON and Markdown reports plus a state summary so you can share, review, or archive threat models.

Instructions

Export strict Threat Composer JSON and Markdown plus a state summary.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_threat_model"
  }
}

Input Schema

Name	Required	Description	Default
`output_path`	No	Optional base filename; directory components are ignored. Omit for a timestamped filename in the selected project's .threatmodel directory.
`include_extended_data`	No	Also write a separate <base>.extended.json server-state snapshot (not importable into Threat Composer); the .tc.json is always strict.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a filesystem write and asserts the output is "strict" (importable) while the extended snapshot is not, but it never says whether an existing file at output_path is overwritten, where the default timestamped file lands, or what failures look like — material gaps for a side-effecting tool.

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?

A single front-loaded sentence with no filler or repetition. It is efficiently sized, though the brevity comes at the cost of the behavioral detail noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, but an unannotated tool that writes files to disk should still disclose overwrite semantics and default location. One sentence covering only output formats is thin for a write operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already fully documented in the schema, including the default path behavior and the extended-data caveat. The description adds only the "strict" guarantee, which reinforces but does not extend the schema's meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition pairs the specific verb "Export" with concrete artifacts: "strict Threat Composer JSON and Markdown plus a state summary." That is enough for an agent to distinguish it from the manage_*/inspect_* siblings, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, no prerequisites, and no mention of alternatives for producing or inspecting model artifacts. The only usage signal is implicit in the word "Export."

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server