red-team-assessmentlisted

# Red-Team Assessment Use the local gtwy stdio MCP server for every red-team and blue-team request. Do not launch a provider CLI directly. Start by calling provider_tool_capabilities to verify the live provider, transport, tool, and target-access surface. The complete gateway CLI roster is Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor. A full red-team assessment dispatches every required reviewer in that roster. If a required provider is unavailable, report a blocker and repair it or obtain explicit user direction. Do not silently call a smaller set "complete." Configured API providers are discovered dynamically with `list_models` and their reported capabilities. They do not provide a local CLI checkout/worktree or native ACP boundary, so they are not silently interchangeable with a required source-inspecting red-team reviewer. ## Security Gate Contract Every red-team prompt must finish with the exact terminal verdict schema: ``` APPROVED_UNCONDITIONALLY | CHANGES_REQUIRED | BLOCKED_EXTERNAL ``` `APPROVED_UNCONDITIONALLY` is allowed only when no unresolved finding or verification gap remains. `CHANGES_REQUIRED` must include evidence-backed findings. `BLOCKED_EXTERNAL` is reserved for a concrete external access, provider, or environment failure with its exact error. Approval with caveats, an accepted-but-unverified claim, a skipped surface, a malformed response, timeout, cancellation, or provider failure is not unconditional approval. Apply these rules: 1. O