Use this when
- Sensitive MCP or AI-tool rollout close to production
- Internal tools where one bad permission decision creates real risk
- Teams that want a written next-step recommendation before a call
Async proposal path
Use this when the team wants a human security decision but is not ready to open the calendar yet. Send the rollout context now, and the next response should clarify fit, scope, and whether the review should stay narrow or escalate.
Started from: MCP Risk Review buyer brief. That context will stay attached to this request.
Keep it short and specific. Rodolf should be able to tell whether this is a fit, what lane it belongs in, and whether the next step should be a call, a review, or a different path.