# Did a recent deploy cause this alert?

Paste an alert or error and your repository. Using your GitHub MCP connection, the agent looks at recently merged pull requests and commits, reads what they changed, and ranks the ones most likely to be related, with its reasoning, as leads for you to check. It needs the GitHub MCP tools list_pull_requests, get_pull_request, get_pull_request_files and list_commits. Tool names are not checked against your server: the agent still runs without any it cannot find, and it says so in its answer when it could not read pull requests.

**Use cases:** Engineering and IT, Monitoring and alerts

**Tags:** tool use, mcp, github, incident, alert, deploy, regression, pull requests, on-call, root cause

[Create this agent](https://seclai.com/agent-examples/create/deploy_alert_suspects)

## How it starts

Trigger: dynamic input.

## What it needs

- **GitHub MCP connection** — Connect a GitHub MCP server under MCP clients first. The agent needs its list_pull_requests, get_pull_request, get_pull_request_files and list_commits tools. These names are not checked against your server: a tool it does not expose is skipped and the agent runs without it.

## Steps

- Find and rank suspect changes
- Show the suspects