The agent determines if specific security threats identified in the threat model are actually mitigated in the current codebase, providing a security verdict.

The agent retrieves the threat model and associated threats, then uses the verify_threats_in_code tool to check if those threats are mitigated in a provided code scan or AST. It can verify a specific threat by ID or dispatch a batch verification for all threats in the diagram. The agent reports the synchronous verdicts or task status back to the user.

• Category: Software development
• Effect: Changes data in your accounts
• MCP servers: Aribot MCP (https://koskamo.com/explore/aribot-mcp)
• Source: Aribot Connector — Documentation (https://api.aribot.ayurak.com/aribot/claude-connector)
• Source quote: "verify_threats_in_code Verify whether modelled STRIDE/LINDDUN threats are mitigated in a scan's uploaded code or AST. If threat_id is provided, returns synchronous verdict; otherwise dispatches batch verification across all diagram threats."
• Playbook page: https://koskamo.com/explore/use-cases/verify-threats-in-code-against-model

Prompt: Verify if the threats in diagram [Diagram ID] are mitigated in the current codebase using the verify_threats_in_code tool. Provide the verification results for each threat.