Operational limits

• MCP_COMMAND_TIMEOUT_MS and MCP_COMMAND_OUTPUT_LIMIT_BYTES bound command execution and captured output. A timed-out, nonzero-exit, or truncated command must be reviewed as incomplete. Tracked subprocess failures are recorded with a failed or cancelled outcome and appear as such in the report evidence index.
• MCP request cancellation and closing an engagement abort active tracked commands. A managed assessment also checks the authoritative parent engagement before every MCP tool dispatch and polls it while Codex runs; closure cancels the container run and closes its worker scope. Scanner subprocesses use the captured scope deadline, including for Nmap, and recheck engagement status immediately before launch.
• rawOptions and scanner features that can override declared targets are restricted, but externally maintained templates and scripts still need operator review.
• Reports are analyst-authored; the server does not infer vulnerability severity from an open port or a scanner template match.
• There is no automatic ticket sync, cloud upload, or proof that the declared authorization reference is valid.