search_previous_threat_models

MCP tool from Ai Security Crew by Srajangpt1

Before creating a new threat model — check if one already exists in Confluence

How to use it

search_previous_threat_models is exposed by the Ai Security Crew MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the search_previous_threat_models tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

Install Ai Security Crew

$docker run --rm -p 8000:8000 mcp-security-review:latest --transport streamable-http

FULL AI SECURITY CREW LISTING

Other tools in Ai Security Crew (9)

assess_ticket_security

Before coding from a Jira ticket — pull security requirements directly from the ticket

lightweight_security_review

Before any coding task — get security requirements and guidelines for your tech stack

perform_threat_model

For significant new features — generate a structured threat model (STRIDE, attack surfaces)

Post-coding

Pre-coding

scan_dependencies

When adding packages — scan for CVEs and check reachability in your code

update_threat_model_file

After performthreatmodel — write the threat model to threat-model.md in the repo

verify_code_security

After generating code — AI-powered security review against OWASP guidelines

verify_packages

When adding packages — confirm they exist with valid versions (catches hallucinated package names)