Verify threats in code against model
The agent determines if specific security threats identified in the threat model are actually mitigated in the current codebase, providing a security verdict.
How it works
Changes data in your accountsSoftware development
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.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Prompt for Verify threats in code against model
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.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
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.Aribot Connector — Documentation