Investigate Smarter from Any Agent: Blast Radius and AI Post-Incident Reviews Come to the PagerDuty MCP Server by Antonella Hidalgo Moreno

PagerDuty announced Early Access to two intelligent tools on its Remote MCP Server: blast radius analysis and AI-drafted post-incident reviews, per a September 15, 2026 blog post by Antonella Hidalgo Moreno. The blast radius tool maps affected-service dependencies, identifies downstream services at risk, surfaces correlation strength, and quantifies user and account impact using PagerDuty's historical incident graph, while the post-incident review tool generates an AI draft with timeline, involved services, participants, and narrative markers pre-populated from the incident record. PagerDuty said the tools will be demonstrated at Dreamforce in partnership with the Slackbot MCP Client, letting a responder run an entire incident without leaving Slackbot.

Investigate Smarter from Any Agent: Blast Radius and AI Post-Incident Reviews Come to the PagerDuty MCP Server Antonella Hidalgo Moreno https://www.pagerduty.com/blog/author/ahmoreno/ September 15, 2026 | 5 min read PagerDuty’s new intelligent Model Context Protocol MCP tools, recently announced in Early Access, are a step toward autonomous operations. Here’s how they help customers get there. The problem isn’t your tools. It’s the tabs between them. Incident response means a lot of tab switching for most teams. Every tab switch is a delay to resolving the issue.. The information needed to resolve the incident exists. It’s just scattered across surfaces that don’t talk to each other, and the responder becomes the integration layer. AI agents are supposed to fix this, but an agent is only as good as the tools it’s given. Early MCP implementations, started as plumbing: API endpoints converted to tools and handed to agents as-is. As the protocol has matured, so has what teams present to agents. At PagerDuty we think of MCP as a product surface, one that speaks to external agents and LLMs on behalf of your operations data, and it deserves the same design rigor as any UI. Tools should be shaped so agents act quickly, consume tokens efficiently, and return repeatable answers across the full range of real operations work: investigation, response, management, analytics, onboarding, reporting, and change management. What we’re announcing Using PagerDuty’s Remote MCP Server, connected agents can run the full incident lifecycle: create, acknowledge, annotate, reassign, and resolve incidents, and look up who’s on call, from supported MCP clients. What’s new is Early Access to two intelligent tools that go beyond operations into investigation and learning: blast radius analysis and AI-drafted post-incident reviews. You can see these tools in action at Dreamforce in partnership with the Slackbot MCP Client, where a responder can run an entire incident, including accessing key data from PagerDuty, without leaving Slackbot. Let’s look at what each tool does. Map the blast radius before your customers do When a service degrades, the immediate question is scope.. Answering that usually requires an expert that might not be available. The blast radius tool answers it from data. Built on PagerDuty’s historical record of which services have had incidents together, it: - Maps the dependencies of the affected service - Identifies which downstream services are at risk - Surfaces correlation strength for each - Quantifies user and account impact. The responder can then ask their agent to check whether any of those correlated services have active incidents right now, which is often how the actual root cause surfaces. This analysis is possible because it draws on PagerDuty’s historical incident graph. Draft the post-incident review without leaving the channel The learning step is the one most teams skip, because by the time the incident resolves, everyone wants to go back to their day. The post-incident review tool helps make sure that step actually happens, right from your MCP client or terminal. A responder can ask their agent to draft a post-incident review for a resolved incident, and PagerDuty generates the AI draft with the timeline, involved services, participants, and narrative markers pre-populated from the incident record. The agent tracks generation progress, and once the draft is ready, the responder can ask for it and get a summary back in the channel, no trip into the PagerDuty UI required. The review gets written while the context is fresh, in the same place the incident was worked, saving time and helping ensure the context is documented for next time. Bringing it together Our MCP covers the day-to-day mechanics of incident management. These two new tools add to what makes PagerDuty different: intelligence derived from years of your incident history, exposed where agents can act on it. Together they make PagerDuty a platform an agent can genuinely operate: the system of record, the historical intelligence layer, and the action surface, all through one well-designed MCP interface. Your team’s surface of choice might be Slackbot today and something else next year. The intelligence underneath shouldn’t care. None of this removes humans from the loop. The agent gathers context, surfaces analysis, and executes the actions a responder asks for. Judgment about what to do stays with the people accountable for the outcome, who now spend their attention on the decision instead of the data gathering. Paving the path to autonomous operations Your team shouldn’t be the integration layer between the systems that hold your incident context. PagerDuty’s approach to autonomous operations: - Puts intelligent agents to work at scale, handling the noise, accelerating resolution, and keeping you in the loop where it matters - Deepens the full incident management lifecycle by empowering teams to resolve incidents faster - Broadens the platform and ecosystem with capabilities that help teams prevent incidents from happening The intelligent MCP tools move us closer to that vision. Ready to see how they can bring PagerDuty’s intelligence to your team’s surface of choice? The blast radius and post-incident review tools are available now in Early Access https://www.pagerduty.com/early-access/ . Reach out to PagerDuty customer support to request access to the preview tool group for your account.