# Egress CI events in the dashboard and over MCP

> The destinations Egress CI jobs send now have a CI tab in the dashboard, the MCP tool egress_ci_events and API filters by repository, workflow, job and run.

The events that [Egress CI](https://developers.openwaf.dev/egress/ci/send-events/) 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_events` filters by `repo`, `workflow`, `job`, `run` and `decision`, and summarizes per repository and destination. `egress_events` is unchanged.
- **API:** `GET …/egress/events` and its stream take `ci_repo`, `ci_workflow`, `ci_job` and `ci_run` (and their `not_` variants) next to `attack_type=egress_ci`.

See [Send events to OpenWAF](https://developers.openwaf.dev/egress/ci/send-events/#see-the-events).