Dropbox bridges security design and code review via MCP + Dash; surfaces threat models at PR time
Dropbox introduced a workflow that connects security design artifacts directly to code review via Model Context Protocol (MCP) and its internal knowledge system, Dash. The problem it solves: threat models, design documents, and security requirements are typically created during design reviews but enforced much later during code review, often without full context. This gap causes reviewers to manually trace security intent back to code changes, increasing the risk of missed requirements. Dropbox's approach uses Dash as a centralized, permission-aware retrieval layer across internal documentation, while MCP provides a standardized protocol for AI systems to access this context within developer workflows.
When a pull request is created, the system identifies relevant code changes and uses MCP-enabled retrieval to surface associated threat models and security requirements from Dash. Security context appears directly in the code review interface, eliminating context-switching across documentation systems. Rather than automating security decisions, the goal is to keep security intent visible at the point of implementation and reduce manual cross-referencing. The solution preserves Dash's enterprise security foundation (permission-aware retrieval, encryption, audit logging), ensuring sensitive documentation remains accessible only to authorized users. Dropbox says the same MCP + Dash pattern can extend to compliance validation, design reviews, and other governance workflows.
For architects: this work demonstrates MCP as a glue layer for agentic workflows in production environments. By standardizing retrieval via MCP, Dropbox decoupled the threat model retrieval system from any specific workflow tool, making the same context layer reusable across code review, compliance, and design review agents. Builders should apply this pattern: define context requirements as MCP resources (threat models, compliance rules, design docs), then compose agents that retrieve and reason about context at decision points. The key design principle: surface evidence and reduce cross-referencing, don't automate security judgment.