The events that Egress CI jobs send with send-events: on were only readable from the API. Now:
- Dashboard: AI egress › CI groups the last 7 days by repository and run, with each destination's job, path, container, decision, reason, detections and traffic, and a link to the run on GitHub. Blocked requests still shows only what the gateway refused to your AI agents.
- MCP:
egress_ci_eventsfilters byrepo,workflow,job,runanddecision, and summarizes per repository and destination.egress_eventsis unchanged. - API:
GET …/egress/eventsand its stream takeci_repo,ci_workflow,ci_jobandci_run(and theirnot_variants) next toattack_type=egress_ci.