Threat Modeling MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FASTMCP_LOG_LEVEL | No | Log level for the FastMCP server | ERROR |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_threat_modeling_planA | Get a comprehensive threat modeling plan. This tool returns a detailed threat modeling plan in markdown format, covering all phases of the threat modeling process. If code is detected in the specified directory, it will automatically run the threat model validation against the code. Args: ctx: MCP context for logging and error handling directory: Directory to check for code files (default: current directory) auto_validate_code: Whether to automatically validate against code if detected (default: True) Returns: A markdown-formatted threat modeling plan |
| add_assumptionA | Add a new assumption to the threat model. Supports batch operations via the 'items' parameter. Assumptions are statements that we accept as true without requiring further validation. They help scope the threat model by establishing boundaries and constraints. For single item: provide description, category, impact, rationale directly. For batch: provide a list of assumption dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling description: Description of the assumption (required for single item mode) category: Category of the assumption (required for single item mode) impact: Impact of the assumption on the threat model (required for single item mode) rationale: Rationale for making this assumption (required for single item mode) items: Optional list of assumption dicts for batch operation Returns: A confirmation message with the assumption ID(s) |
| list_assumptionsA | List all current assumptions in the threat model. Args: ctx: MCP context for logging and error handling category: Optional category to filter assumptions Returns: A markdown-formatted list of assumptions |
| get_assumptionA | Get details about a specific assumption. Args: ctx: MCP context for logging and error handling id: ID of the assumption to retrieve Returns: A markdown-formatted description of the assumption |
| update_assumptionA | Update an existing assumption. Supports batch operations via the 'items' parameter. For single item: provide id and fields to update directly. For batch: provide a list of assumption dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the assumption to update (required for single item mode) description: New description of the assumption category: New category of the assumption impact: New impact of the assumption rationale: New rationale for the assumption items: Optional list of assumption dicts for batch update Returns: A confirmation message |
| delete_assumptionB | Delete an assumption from the threat model. Supports batch operations via the 'ids' parameter. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the assumption to delete (required for single item mode) ids: Optional list of assumption IDs for batch deletion Returns: A confirmation message |
| set_business_contextA | Set the business context with description and all features in one call. This streamlined tool sets the business context description and all business features in a single call, eliminating the need for the clarification questions workflow. Args: ctx: MCP context for logging and error handling description: Business context description industry_sector: Industry sector (optional) data_sensitivity: Data sensitivity level (optional) user_base_size: User base size (optional) geographic_scope: Geographic scope (optional) regulatory_requirements: Regulatory requirements, comma-separated (optional) system_criticality: System criticality (optional) financial_impact: Financial impact of breach (optional) authentication_requirement: Authentication requirement (optional) deployment_environment: Deployment environment (optional) integration_complexity: Integration complexity (optional) Returns: A confirmation message with the number of features configured |
| get_business_contextA | Get the business context. This tool returns the business context created from the answers to the clarification questions. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted business context |
| clear_business_contextA | Clear the business context. This tool clears the business context, description, and clarification questions. Args: ctx: MCP context for logging and error handling Returns: A confirmation message |
| get_business_context_featuresB | Get all business context features with descriptions. This tool returns all available features of the business context with descriptions of what each feature represents. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted list of business context features with descriptions |
| validate_business_context_completenessA | Validate that all business context features are set before proceeding to next phase. This tool validates that all required business context features have been set and returns a clear message indicating whether the business context is complete or what features are still missing. Args: ctx: MCP context for logging and error handling Returns: A validation message indicating if business context is complete |
| get_business_context_analysis_planB | Get a comprehensive business context analysis plan. This tool returns a detailed plan for analyzing business context descriptions using AI-powered analysis to categorize business features. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted business context analysis plan with prompts for LLM analysis |
| add_componentA | Add a new component to the architecture. Supports batch operations via the 'items' parameter. This tool adds one or more components to the system architecture. For single item: provide name, type, and optional fields directly. For batch: provide a list of component dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling name: Name of the component (required for single item mode) type: Type of the component (required for single item mode) service_provider: Provider of the service (e.g., 'AWS', 'Azure', 'GCP') specific_service: Specific service name (e.g., 'EC2', 'S3', 'Lambda') version: Version of the component description: Description of the component configuration: Configuration details of the component items: Optional list of component dicts for batch operation Returns: A confirmation message with the component ID(s) |
| update_componentA | Update an existing component in the architecture. Supports batch operations via the 'items' parameter. This tool updates one or more existing components in the system architecture. For single item: provide id and fields to update directly. For batch: provide a list of component dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the component to update (required for single item mode) name: New name of the component type: New type of the component service_provider: New provider of the service specific_service: New specific service name version: New version of the component description: New description of the component configuration: New configuration details of the component items: Optional list of component dicts for batch update Returns: A confirmation message |
| list_componentsA | List all components in the architecture. This tool lists all components in the system architecture. Args: ctx: MCP context for logging and error handling type: Optional type to filter components Returns: A markdown-formatted list of components |
| delete_componentA | Delete a component from the architecture. Supports batch operations via the 'ids' parameter. This tool deletes one or more components from the system architecture. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the component to delete (required for single item mode) ids: Optional list of component IDs for batch deletion Returns: A confirmation message |
| add_connectionA | Add a new connection to the architecture. Supports batch operations via the 'items' parameter. This tool adds one or more connections between components in the system architecture. For single item: provide source_id, destination_id, and optional fields directly. For batch: provide a list of connection dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling source_id: ID of the source component (required for single item mode) destination_id: ID of the destination component (required for single item mode) protocol: Protocol used for the connection (e.g., 'HTTP', 'HTTPS', 'TCP') port: Port used for the connection encryption: Whether the connection is encrypted description: Description of the connection items: Optional list of connection dicts for batch operation Returns: A confirmation message with the connection ID(s) |
| update_connectionA | Update an existing connection in the architecture. Supports batch operations via the 'items' parameter. This tool updates one or more existing connections in the system architecture. For single item: provide id and fields to update directly. For batch: provide a list of connection dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the connection to update (required for single item mode) source_id: New ID of the source component destination_id: New ID of the destination component protocol: New protocol used for the connection port: New port used for the connection encryption: New encryption status description: New description of the connection items: Optional list of connection dicts for batch update Returns: A confirmation message |
| list_connectionsA | List all connections in the architecture. This tool lists all connections in the system architecture. Args: ctx: MCP context for logging and error handling component_id: Optional component ID to filter connections Returns: A markdown-formatted list of connections |
| delete_connectionA | Delete a connection from the architecture. Supports batch operations via the 'ids' parameter. This tool deletes one or more connections from the system architecture. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the connection to delete (required for single item mode) ids: Optional list of connection IDs for batch deletion Returns: A confirmation message |
| add_data_storeA | Add a new data store to the architecture. Supports batch operations via the 'items' parameter. This tool adds one or more data stores to the system architecture. For single item: provide name, type, classification, and optional fields directly. For batch: provide a list of data store dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling name: Name of the data store (required for single item mode) type: Type of the data store (required for single item mode) classification: Classification of the data (required for single item mode) encryption_at_rest: Whether the data is encrypted at rest backup_frequency: Frequency of backups (e.g., 'Hourly', 'Daily', 'Weekly') description: Description of the data store items: Optional list of data store dicts for batch operation Returns: A confirmation message with the data store ID(s) |
| update_data_storeA | Update an existing data store in the architecture. Supports batch operations via the 'items' parameter. This tool updates one or more existing data stores in the system architecture. For single item: provide id and fields to update directly. For batch: provide a list of data store dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the data store to update (required for single item mode) name: New name of the data store type: New type of the data store classification: New classification of the data encryption_at_rest: New encryption status backup_frequency: New frequency of backups description: New description of the data store items: Optional list of data store dicts for batch update Returns: A confirmation message |
| list_data_storesA | List all data stores in the architecture. This tool lists all data stores in the system architecture. Args: ctx: MCP context for logging and error handling type: Optional type to filter data stores Returns: A markdown-formatted list of data stores |
| delete_data_storeA | Delete a data store from the architecture. Supports batch operations via the 'ids' parameter. This tool deletes one or more data stores from the system architecture. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the data store to delete (required for single item mode) ids: Optional list of data store IDs for batch deletion Returns: A confirmation message |
| get_architecture_analysis_planC | Get a comprehensive architecture analysis plan. This tool returns a detailed plan for analyzing system architecture for security concerns using AI-powered analysis with AWS documentation validation. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted architecture analysis plan with prompts for LLM analysis |
| clear_architectureA | Clear the architecture. This tool clears all components, connections, and data stores from the architecture. Args: ctx: MCP context for logging and error handling Returns: A confirmation message |
| add_threat_actorA | Add a new threat actor. Supports batch operations via the 'items' parameter. This tool adds one or more threat actors to the threat model. For single item: provide name, type, capability_level, motivations, resources directly. For batch: provide a list of threat actor dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling name: Name of the threat actor (required for single item mode) type: Type of the threat actor (required for single item mode) capability_level: Capability level of the threat actor (required for single item mode) motivations: Motivations of the threat actor (required for single item mode) resources: Resources available to the threat actor (required for single item mode) description: Description of the threat actor priority: Priority of the threat actor (1-10, 0 means not ranked) relevance_score: Relevance score of the threat actor (0.0-1.0) is_relevant: Whether the threat actor is relevant to the system items: Optional list of threat actor dicts for batch operation Returns: A confirmation message with the threat actor ID(s) |
| update_threat_actorA | Update an existing threat actor. Supports batch operations via the 'items' parameter. This tool updates one or more existing threat actors in the threat model. For single item: provide id and fields to update directly. For batch: provide a list of threat actor dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the threat actor to update (required for single item mode) name: New name of the threat actor type: New type of the threat actor capability_level: New capability level of the threat actor motivations: New motivations of the threat actor resources: New resources available to the threat actor description: New description of the threat actor priority: New priority of the threat actor (1-10) relevance_score: New relevance score of the threat actor (0.0-1.0) is_relevant: New relevance status of the threat actor items: Optional list of threat actor dicts for batch update Returns: A confirmation message |
| list_threat_actorsB | List all threat actors. This tool lists all threat actors in the threat model. Args: ctx: MCP context for logging and error handling type: Optional type to filter threat actors relevant_only: Whether to only show relevant threat actors Returns: A markdown-formatted list of threat actors |
| get_threat_actorA | Get details about a specific threat actor. This tool retrieves details about a specific threat actor in the threat model. Args: ctx: MCP context for logging and error handling id: ID of the threat actor to retrieve Returns: A markdown-formatted description of the threat actor |
| delete_threat_actorA | Delete a threat actor. Supports batch operations via the 'ids' parameter. This tool deletes one or more threat actors from the threat model. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the threat actor to delete (required for single item mode) ids: Optional list of threat actor IDs for batch deletion Returns: A confirmation message |
| set_threat_actor_relevanceC | Set the relevance of a threat actor. This tool sets whether a threat actor is relevant to the system. Args: ctx: MCP context for logging and error handling id: ID of the threat actor is_relevant: Whether the threat actor is relevant to the system Returns: A confirmation message |
| set_threat_actor_priorityC | Set the priority of a threat actor. This tool sets the priority of a threat actor in the threat model. Args: ctx: MCP context for logging and error handling id: ID of the threat actor priority: Priority of the threat actor (1-10) Returns: A confirmation message |
| analyze_threat_actorsA | Analyze the threat actors. This tool analyzes the threat actors in the threat model and provides recommendations. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted analysis of the threat actors |
| reset_threat_actorsB | Reset the threat actors to the default set. This tool resets the threat actors to the default set. Args: ctx: MCP context for logging and error handling Returns: A confirmation message |
| clear_threat_actorsB | Clear all threat actors. This tool clears all threat actors from the threat model. Args: ctx: MCP context for logging and error handling Returns: A confirmation message |
| add_trust_zoneA | Add a new trust zone. Supports batch operations via the 'items' parameter. This tool adds one or more trust zones to the system architecture. For single item: provide name, trust_level, and optional fields directly. For batch: provide a list of trust zone dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling name: Name of the trust zone (required for single item mode) trust_level: Trust level of the zone (required for single item mode) description: Description of the trust zone items: Optional list of trust zone dicts for batch operation Returns: A confirmation message with the trust zone ID(s) |
| update_trust_zoneA | Update an existing trust zone. Supports batch operations via the 'items' parameter. This tool updates one or more existing trust zones in the system architecture. For single item: provide id and fields to update directly. For batch: provide a list of trust zone dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the trust zone to update (required for single item mode) name: New name of the trust zone trust_level: New trust level of the zone description: New description of the trust zone items: Optional list of trust zone dicts for batch update Returns: A confirmation message |
| list_trust_zonesA | List all trust zones. This tool lists all trust zones in the system architecture. Args: ctx: MCP context for logging and error handling trust_level: Optional trust level to filter zones Returns: A markdown-formatted list of trust zones |
| get_trust_zoneB | Get details about a specific trust zone. This tool retrieves details about a specific trust zone in the system architecture. Args: ctx: MCP context for logging and error handling id: ID of the trust zone to retrieve Returns: A markdown-formatted description of the trust zone |
| delete_trust_zoneA | Delete a trust zone. Supports batch operations via the 'ids' parameter. This tool deletes one or more trust zones from the system architecture. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the trust zone to delete (required for single item mode) ids: Optional list of trust zone IDs for batch deletion Returns: A confirmation message |
| add_component_to_zoneA | Add a component to a trust zone. Supports batch operations via the 'items' parameter. This tool adds one or more components to trust zones in the system architecture. For single item: provide zone_id and component_id directly. For batch: provide a list of dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling zone_id: ID of the trust zone (required for single item mode) component_id: ID of the component to add (required for single item mode) items: Optional list of zone-component pair dicts for batch operation Returns: A confirmation message |
| remove_component_from_zoneC | Remove a component from a trust zone. This tool removes a component from a trust zone in the system architecture. Args: ctx: MCP context for logging and error handling zone_id: ID of the trust zone component_id: ID of the component to remove Returns: A confirmation message |
| add_crossing_pointA | Add a new crossing point. Supports batch operations via the 'items' parameter. This tool adds one or more crossing points between trust zones in the system architecture. For single item: provide source_zone_id, destination_zone_id, and optional fields directly. For batch: provide a list of crossing point dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling source_zone_id: ID of the source trust zone (required for single item mode) destination_zone_id: ID of the destination trust zone (required for single item mode) authentication_method: Authentication method used at the crossing point authorization_method: Authorization method used at the crossing point description: Description of the crossing point items: Optional list of crossing point dicts for batch operation Returns: A confirmation message with the crossing point ID(s) |
| update_crossing_pointA | Update an existing crossing point. Supports batch operations via the 'items' parameter. This tool updates one or more existing crossing points in the system architecture. For single item: provide id and fields to update directly. For batch: provide a list of crossing point dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the crossing point to update (required for single item mode) source_zone_id: New ID of the source trust zone destination_zone_id: New ID of the destination trust zone authentication_method: New authentication method authorization_method: New authorization method description: New description of the crossing point items: Optional list of crossing point dicts for batch update Returns: A confirmation message |
| list_crossing_pointsA | List all crossing points. This tool lists all crossing points in the system architecture. Args: ctx: MCP context for logging and error handling zone_id: Optional trust zone ID to filter crossing points Returns: A markdown-formatted list of crossing points |
| get_crossing_pointC | Get details about a specific crossing point. This tool retrieves details about a specific crossing point in the system architecture. Args: ctx: MCP context for logging and error handling id: ID of the crossing point to retrieve Returns: A markdown-formatted description of the crossing point |
| delete_crossing_pointB | Delete a crossing point. Supports batch operations via the 'ids' parameter. This tool deletes one or more crossing points from the system architecture. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the crossing point to delete (required for single item mode) ids: Optional list of crossing point IDs for batch deletion Returns: A confirmation message |
| add_conn_to_crossingA | Add a connection to a crossing point. Supports batch operations via the 'items' parameter. This tool adds one or more connections to crossing points in the system architecture. For single item: provide crossing_point_id and connection_id directly. For batch: provide a list of dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling crossing_point_id: ID of the crossing point (required for single item mode) connection_id: ID of the connection to add (required for single item mode) items: Optional list of crossing-point-connection pair dicts for batch operation Returns: A confirmation message |
| remove_conn_from_crossingB | Remove a connection from a crossing point. This tool removes a connection from a crossing point in the system architecture. Args: ctx: MCP context for logging and error handling crossing_point_id: ID of the crossing point connection_id: ID of the connection to remove Returns: A confirmation message |
| add_trust_boundaryA | Add a new trust boundary. Supports batch operations via the 'items' parameter. This tool adds one or more trust boundaries to the system architecture. For single item: provide name, type, and optional fields directly. For batch: provide a list of trust boundary dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling name: Name of the trust boundary (required for single item mode) type: Type of the trust boundary (required for single item mode) crossing_point_ids: IDs of crossing points that cross this boundary controls: Security controls implemented at this boundary description: Description of the trust boundary items: Optional list of trust boundary dicts for batch operation Returns: A confirmation message with the trust boundary ID(s) |
| update_trust_boundaryA | Update an existing trust boundary. Supports batch operations via the 'items' parameter. This tool updates one or more existing trust boundaries in the system architecture. For single item: provide id and fields to update directly. For batch: provide a list of trust boundary dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the trust boundary to update (required for single item mode) name: New name of the trust boundary type: New type of the trust boundary crossing_point_ids: New IDs of crossing points controls: New security controls description: New description of the trust boundary items: Optional list of trust boundary dicts for batch update Returns: A confirmation message |
| list_trust_boundariesB | List all trust boundaries. This tool lists all trust boundaries in the system architecture. Args: ctx: MCP context for logging and error handling type: Optional type to filter trust boundaries Returns: A markdown-formatted list of trust boundaries |
| get_trust_boundaryA | Get details about a specific trust boundary. This tool retrieves details about a specific trust boundary in the system architecture. Args: ctx: MCP context for logging and error handling id: ID of the trust boundary to retrieve Returns: A markdown-formatted description of the trust boundary |
| delete_trust_boundaryA | Delete a trust boundary. Supports batch operations via the 'ids' parameter. This tool deletes one or more trust boundaries from the system architecture. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the trust boundary to delete (required for single item mode) ids: Optional list of trust boundary IDs for batch deletion Returns: A confirmation message |
| get_trust_boundary_analysis_planA | Get a comprehensive trust boundary analysis plan. This tool returns a detailed plan for analyzing trust boundaries for security concerns using AI-powered analysis with AWS documentation validation. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted trust boundary analysis plan with prompts for LLM analysis |
| clear_trust_boundariesA | Clear all trust boundaries. This tool clears all trust boundaries, crossing points, and trust zones from the system architecture. Args: ctx: MCP context for logging and error handling Returns: A confirmation message |
| get_trust_boundary_detection_planA | Get a comprehensive trust boundary detection plan. This tool returns a detailed plan for detecting trust boundaries from architecture components using AI-powered analysis with step-by-step prompts and guidance. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted plan with prompts for LLM-powered trust boundary detection |
| add_assetA | Add a new asset to the system. Supports batch operations via the 'items' parameter. This tool adds one or more assets to the system. For single item: provide name, type, classification, and optional fields directly. For batch: provide a list of asset dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling name: Name of the asset (required for single item mode) type: Type of the asset (e.g., 'Data', 'Credential', 'Process') (required for single item mode) classification: Classification of the asset (e.g., 'Public', 'Confidential') (required for single item mode) lifecycle_state: Current lifecycle state of the asset description: Description of the asset owner: Owner of the asset sensitivity: Sensitivity level of the asset (1-5) criticality: Criticality level of the asset (1-5) metadata: Additional metadata for the asset items: Optional list of asset dicts for batch operation Returns: A confirmation message with the asset ID(s) |
| update_assetA | Update an existing asset. Supports batch operations via the 'items' parameter. This tool updates one or more existing assets in the system. For single item: provide id and fields to update directly. For batch: provide a list of asset dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the asset to update (required for single item mode) name: New name of the asset type: New type of the asset classification: New classification of the asset lifecycle_state: New lifecycle state of the asset description: New description of the asset owner: New owner of the asset sensitivity: New sensitivity level of the asset criticality: New criticality level of the asset metadata: New metadata for the asset items: Optional list of asset dicts for batch update Returns: A confirmation message |
| list_assetsA | List all assets in the system. This tool lists all assets in the system, optionally filtered by type or classification. Args: ctx: MCP context for logging and error handling type: Optional type to filter assets classification: Optional classification to filter assets Returns: A markdown-formatted list of assets |
| get_assetA | Get details about a specific asset. This tool retrieves details about a specific asset in the system. Args: ctx: MCP context for logging and error handling id: ID of the asset to retrieve Returns: A markdown-formatted description of the asset |
| delete_assetA | Delete an asset from the system. Supports batch operations via the 'ids' parameter. This tool deletes one or more assets from the system. Assets cannot be deleted if used in any flows. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the asset to delete (required for single item mode) ids: Optional list of asset IDs for batch deletion Returns: A confirmation message |
| add_flowA | Add a new asset flow to the system. Supports batch operations via the 'items' parameter. This tool adds one or more asset flows to the system. For single item: provide asset_id, source_id, destination_id, and optional fields directly. For batch: provide a list of flow dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling asset_id: ID of the asset being transferred (required for single item mode) source_id: ID of the source component or trust zone (required for single item mode) destination_id: ID of the destination component or trust zone (required for single item mode) transformation_type: Type of transformation applied to the asset controls: List of security controls applied to the flow description: Description of the flow protocol: Protocol used for the flow encryption: Whether the flow is encrypted authenticated: Whether the flow is authenticated authorized: Whether the flow is authorized validated: Whether the flow is validated risk_level: Risk level of the flow (1-5) items: Optional list of flow dicts for batch operation Returns: A confirmation message with the flow ID(s) |
| update_flowA | Update an existing asset flow. Supports batch operations via the 'items' parameter. This tool updates one or more existing asset flows in the system. For single item: provide id and fields to update directly. For batch: provide a list of flow dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the flow to update (required for single item mode) asset_id: New ID of the asset being transferred source_id: New ID of the source component or trust zone destination_id: New ID of the destination component or trust zone transformation_type: New type of transformation applied to the asset controls: New list of security controls applied to the flow description: New description of the flow protocol: New protocol used for the flow encryption: New encryption status authenticated: New authentication status authorized: New authorization status validated: New validation status risk_level: New risk level of the flow (1-5) items: Optional list of flow dicts for batch update Returns: A confirmation message |
| list_flowsA | List all asset flows in the system. This tool lists all asset flows in the system, optionally filtered by asset ID or component ID. Args: ctx: MCP context for logging and error handling asset_id: Optional asset ID to filter flows component_id: Optional component ID to filter flows Returns: A markdown-formatted list of flows |
| get_flowB | Get details about a specific asset flow. This tool retrieves details about a specific asset flow in the system. Args: ctx: MCP context for logging and error handling id: ID of the flow to retrieve Returns: A markdown-formatted description of the flow |
| delete_flowA | Delete an asset flow from the system. Supports batch operations via the 'ids' parameter. This tool deletes one or more asset flows from the system. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the flow to delete (required for single item mode) ids: Optional list of flow IDs for batch deletion Returns: A confirmation message |
| get_asset_flow_analysis_planA | Get a comprehensive asset flow analysis plan. This tool returns a detailed plan for analyzing asset flows for security concerns using AI-powered analysis with AWS documentation validation. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted asset flow analysis plan with prompts for LLM analysis |
| clear_asset_flowsC | Clear all assets and flows from the system. This tool clears all assets and flows from the system. Args: ctx: MCP context for logging and error handling Returns: A confirmation message |
| reset_asset_flowsC | Reset assets and flows to the default set. This tool resets assets and flows to the default set. Args: ctx: MCP context for logging and error handling Returns: A confirmation message |
| add_threatA | Add a new threat to the model. Supports batch operations via the 'items' parameter. This tool adds one or more threats to the threat model. IMPORTANT: Each text field must be 200 characters or fewer to comply with the Threat Composer schema. For single item: provide threat_source, prerequisites, threat_action, threat_impact directly. For batch: provide a list of threat dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling threat_source: Source of the threat, max 200 chars (required for single item mode) prerequisites: Prerequisites for the threat, max 200 chars (required for single item mode) threat_action: Action performed by the threat, max 200 chars (required for single item mode) threat_impact: Impact of the threat, max 200 chars (required for single item mode) category: STRIDE category of the threat severity: Severity of the threat likelihood: Likelihood of the threat affected_components: List of component IDs affected by the threat affected_assets: List of asset IDs affected by the threat tags: List of tags for the threat items: Optional list of threat dicts for batch operation Returns: A confirmation message with the threat ID(s) |
| list_threatsA | List all threats in the model. This tool lists all threats in the threat model, optionally filtered by category, severity, or status. Args: ctx: MCP context for logging and error handling category: Optional category to filter threats severity: Optional severity to filter threats status: Optional status to filter threats Returns: A markdown-formatted list of threats |
| get_threatA | Get details about a specific threat. This tool retrieves details about a specific threat in the threat model. Args: ctx: MCP context for logging and error handling id: ID of the threat to retrieve Returns: A markdown-formatted description of the threat |
| update_threatA | Update an existing threat. Supports batch operations via the 'items' parameter. This tool updates one or more existing threats in the threat model. IMPORTANT: Each text field must be 200 characters or fewer to comply with the Threat Composer schema. For single item: provide id and fields to update directly. For batch: provide a list of threat dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the threat to update (required for single item mode) threat_source: New source of the threat, max 200 chars prerequisites: New prerequisites for the threat, max 200 chars threat_action: New action performed by the threat, max 200 chars threat_impact: New impact of the threat, max 200 chars category: New STRIDE category of the threat severity: New severity of the threat likelihood: New likelihood of the threat status: New status of the threat affected_components: New list of component IDs affected by the threat affected_assets: New list of asset IDs affected by the threat tags: New list of tags for the threat items: Optional list of threat dicts for batch update Returns: A confirmation message |
| delete_threatA | Delete a threat from the model. Supports batch operations via the 'ids' parameter. This tool deletes one or more threats from the threat model. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the threat to delete (required for single item mode) ids: Optional list of threat IDs for batch deletion Returns: A confirmation message |
| add_mitigationA | Add a new mitigation to the model. Supports batch operations via the 'items' parameter. This tool adds one or more mitigations to the threat model. For single item: provide content and optional fields directly. For batch: provide a list of mitigation dicts in the 'items' parameter. Args: ctx: MCP context for logging and error handling content: Content of the mitigation (required for single item mode) type: Type of the mitigation status: Status of the mitigation implementation_details: Implementation details of the mitigation cost: Cost of the mitigation effectiveness: Effectiveness of the mitigation metadata: Metadata for the mitigation items: Optional list of mitigation dicts for batch operation Returns: A confirmation message with the mitigation ID(s) |
| list_mitigationsA | List all mitigations in the model. This tool lists all mitigations in the threat model, optionally filtered by type or status. Args: ctx: MCP context for logging and error handling type: Optional type to filter mitigations status: Optional status to filter mitigations Returns: A markdown-formatted list of mitigations |
| get_mitigationA | Get details about a specific mitigation. This tool retrieves details about a specific mitigation in the threat model. Args: ctx: MCP context for logging and error handling id: ID of the mitigation to retrieve Returns: A markdown-formatted description of the mitigation |
| update_mitigationA | Update an existing mitigation. Supports batch operations via the 'items' parameter. This tool updates one or more existing mitigations in the threat model. For single item: provide id and fields to update directly. For batch: provide a list of mitigation dicts in the 'items' parameter (each must include 'id'). Args: ctx: MCP context for logging and error handling id: ID of the mitigation to update (required for single item mode) content: New content of the mitigation type: New type of the mitigation status: New status of the mitigation implementation_details: New implementation details of the mitigation cost: New cost of the mitigation effectiveness: New effectiveness of the mitigation metadata: New metadata for the mitigation items: Optional list of mitigation dicts for batch update Returns: A confirmation message |
| delete_mitigationA | Delete a mitigation from the model. Supports batch operations via the 'ids' parameter. This tool deletes one or more mitigations from the threat model. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter. Args: ctx: MCP context for logging and error handling id: ID of the mitigation to delete (required for single item mode) ids: Optional list of mitigation IDs for batch deletion Returns: A confirmation message |
| link_mitigation_to_threatB | Link a mitigation to a threat. This tool links a mitigation to a threat in the threat model. Args: ctx: MCP context for logging and error handling mitigation_id: ID of the mitigation to link threat_id: ID of the threat to link to Returns: A confirmation message |
| unlink_mitigation_from_threatB | Unlink a mitigation from a threat. This tool unlinks a mitigation from a threat in the threat model. Args: ctx: MCP context for logging and error handling mitigation_id: ID of the mitigation to unlink threat_id: ID of the threat to unlink from Returns: A confirmation message |
| export_comprehensive_threat_modelA | Export comprehensive threat model with all global variables to Threat Composer JSON format. This tool exports the complete threat model including all global variables from all phases of the threat modeling process. It collects business context, assumptions, architecture, threat actors, trust boundaries, asset flows, threats, mitigations, and phase progress. Args: ctx: MCP context for logging and error handling output_path: Path to save the exported threat model (will be saved in .threatmodel directory) include_extended_data: Whether to include extended data beyond standard Threat Composer format Returns: A comprehensive export summary with details about what was exported |
| get_data_model_typesB | Get available types for a data model. This tool returns the available types for a specified data model. Args: ctx: MCP context for logging and error handling model_name: Name of the data model to get types for Returns: A markdown-formatted list of available types |
| list_data_modelsA | List all available data models. This tool lists all available data models that can be used with get_data_model_types. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted list of available data models |
| validate_security_controlsA | Check what security controls are implemented in code and update threat model. Given the current threats and mitigations in the threat model, analyze the codebase to determine what's actually implemented and update the threat model accordingly. The agent should autonomously decide how to analyze the code. Args: ctx: MCP context for logging and error handling code_directory: Directory containing code to analyze file_patterns: Optional list of file patterns to include (e.g., [".py", ".js"]) Returns: Simple instruction for autonomous analysis |
| validate_threat_remediationA | Check if specific threats are remediated in code and update threat model. Given specific threat IDs, analyze the codebase to determine if these threats are mitigated by existing code and update the threat model accordingly. Args: ctx: MCP context for logging and error handling code_directory: Directory containing code to analyze threat_ids: List of threat IDs to validate Returns: Simple instruction for autonomous threat-specific analysis |
| generate_remediation_reportA | Generate a prompt for LLM to create a comprehensive remediation report. This tool generates a prompt for LLM to create a report showing which threats are remediated by existing security controls in the code, which are partially remediated, and which require implementation. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted prompt for LLM to generate a remediation report |
| validate_threat_model_against_codeA | Validate the threat model against the actual codebase. This tool analyzes the codebase to determine which threats are already mitigated by existing security controls, and generates a comprehensive report. Args: ctx: MCP context for logging and error handling code_directory: Directory containing code to analyze file_patterns: Optional list of file patterns to include (e.g., [".py", ".js"]) Returns: A markdown-formatted validation report |
| export_threat_model_with_remediation_statusA | Export the threat model with remediation status. This tool exports the threat model with information about which threats are already remediated by existing security controls. Args: ctx: MCP context for logging and error handling output_path: Path to save the exported threat model Returns: A confirmation message |
| get_phase_1_guidanceA | Get detailed guidance for Phase 1: Business Context Analysis. This tool provides step-by-step guidance for conducting business context analysis, including objectives, steps, tools to use, and expected outputs. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted guide for Phase 1 |
| get_phase_2_guidanceA | Get detailed guidance for Phase 2: Architecture Analysis. This tool provides step-by-step guidance for conducting architecture analysis, including objectives, steps, tools to use, and expected outputs. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted guide for Phase 2 |
| get_phase_3_guidanceA | Get detailed guidance for Phase 3: Threat Actor Analysis. This tool provides step-by-step guidance for conducting threat actor analysis, including objectives, steps, tools to use, and expected outputs. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted guide for Phase 3 |
| get_phase_4_guidanceA | Get detailed guidance for Phase 4: Trust Boundary Analysis. This tool provides step-by-step guidance for conducting trust boundary analysis, including objectives, steps, tools to use, and expected outputs. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted guide for Phase 4 |
| get_phase_5_guidanceA | Get detailed guidance for Phase 5: Asset Flow Analysis. This tool provides step-by-step guidance for conducting asset flow analysis, including objectives, steps, tools to use, and expected outputs. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted guide for Phase 5 |
| get_phase_6_guidanceA | Get detailed guidance for Phase 6: Threat Identification. This tool provides step-by-step guidance for conducting threat identification, including objectives, steps, tools to use, and expected outputs. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted guide for Phase 6 |
| get_phase_7_guidanceA | Get detailed guidance for Phase 7: Mitigation Planning. This tool provides step-by-step guidance for conducting mitigation planning, including objectives, steps, tools to use, and expected outputs. The next steps are conditional based on whether code is detected in the project. Args: ctx: MCP context for logging and error handling directory: Directory to check for code files (default: current directory) Returns: A markdown-formatted guide for Phase 7 with conditional next steps |
| get_phase_7_5_guidanceA | Get detailed guidance for Phase 7.5: Code Validation Analysis. This tool provides step-by-step guidance for conducting code validation analysis, including objectives, steps, tools to use, and expected outputs. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted guide for Phase 7.5 |
| get_phase_8_guidanceA | Get detailed guidance for Phase 8: Residual Risk Analysis. This tool provides step-by-step guidance for conducting residual risk analysis, including objectives, steps, tools to use, and expected outputs. Args: ctx: MCP context for logging and error handling Returns: A markdown-formatted guide for Phase 8 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/awslabs/threat-modeling-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server