Cloud findings

Use the connected Codex Security Cloud tools for existing findings and scans. This workflow only reads data. Do not launch or cancel scans, close or edit findings, generate patches, run verification, upload results, or send notifications. The connector has other tools that can write; connecting it does not make those tools part of this workflow. Local security scans do not need Cloud connected.

Before using the tools and filters below, discover the relevant defense_factory_* tools through tool search and inspect their current schemas. Use only exposed tools and parameters. If a requested capability is unavailable, explain which part cannot be completed and continue with the supported parts of the request. A report available only through a missing evidence reader remains unread; a missing assignee filter cannot perform an assignee-filtered query. Do not silently drop a requested filter or describe a partial answer as complete.

Resolve the account and repository

Call defense_factory_bootstrap before data reads. Reuse its result within the request; check again after the user changes accounts or workspaces, completes setup, or a permission error requires renewed context. Use its identity and accountId as the selected account context. A workspace ID in a prompt or link does not override the signed-in account.