Sign in Book a demo
Back to Tools
Developer Tools OAuth
Build Your Agent View PagerDuty Docs
pagerduty logo

PagerDuty MCP Tools for AI Agents

Let an agent find incidents, inspect activity, check on-call coverage, and acknowledge, resolve, or reassign them.

Available Tools

16 tools available in this integration

Pagerduty.GetEscalationPolicy

Get a single escalation policy by ID.

Pagerduty.GetIncident

Get a single incident by ID.

Pagerduty.GetService

Get a single service by ID.

Pagerduty.GetTeam

Get a single team by ID including members and linked resources.

Pagerduty.ListEscalationPolicies

List escalation policies.

Pagerduty.ListIncidents

List incidents with optional status, urgency, service, team, and time filters.

Pagerduty.ListLogEntries

List log entries (activity feed) showing recent incident events.

Pagerduty.ListOncalls

List on-call entries with optional filters.

Pagerduty.ListSchedules

List schedules.

Pagerduty.ListServices

List services with optional name search.

Pagerduty.ListTeams

List teams.

Pagerduty.ListUsers

List users.

Pagerduty.ReassignIncident

Reassign an incident to a specific user without changing its status.

Pagerduty.SearchUsers

Search users using local fuzzy matching on name/email.

Pagerduty.UpdateIncidentStatus

Update an incident's status (acknowledge, resolve/close, or reopen).

Pagerduty.Whoami

Get the authenticated PagerDuty user's profile with contact and notification summaries.

Working directly against the raw API? 374 more tools in the PagerDuty API server →

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find every unassigned high-urgency incident for the payments service and propose the right responder." Arcade helps it use the right PagerDuty tools without guessing incident, service, or user IDs.

Up to 100x fewer tokens

PagerDuty list and search actions return focused incident, service, team, and on-call metadata, while single-record reads provide detail when needed. The agent can triage incidents without loading every activity feed or team record.

Complete the workflow end to end

Find the incident, inspect its activity, check the on-call responder, reassign it, and update its status through one toolkit designed around the complete incident-response task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing PagerDuty

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For PagerDuty, you can implement some of these policies:

Access when tools are listed for a user
  • Hide Pagerduty.UpdateIncidentStatus from agents unless the roles your IDP marks as incident commanders or service owners are active, so an agent cannot resolve or reopen incidents outside its authority.
  • Restrict Pagerduty.ReassignIncident to agents operating under your incident-management role, so an agent cannot move incidents to another responder without the right operational authority.
Pre-execution before each tool call
  • Require human approval before Pagerduty.UpdateIncidentStatus resolves or reopens an incident, so an agent cannot close an active incident or revive a closed one without review.
  • Block Pagerduty.ReassignIncident when the target user is not assigned to the incident's service team, so an agent cannot route an incident to an unrelated responder.
Post-execution after the tool returns
  • Redact incident descriptions, response notes, and embedded email addresses from Pagerduty.GetIncident before they reach the model, so private customer or infrastructure details are not exposed in context.
  • Strip personal email addresses and phone numbers from Pagerduty.GetTeam results, leaving team membership and linked resources without private contact details.
  • Redact contact details and notification endpoints from Pagerduty.Whoami, so the model can identify the authenticated user without receiving private routing information.

How to use PagerDuty with your agent

Connect PagerDuty to your MCP client and follow the setup from authorization to your first incident query.

Your questions, answered

A PagerDuty MCP server exposes PagerDuty capabilities as structured tools that an AI agent can call through the Model Context Protocol. After a user authorizes their PagerDuty account, the agent can inspect incidents, on-call schedules, services, teams, and escalation policies, and perform permitted incident updates.

PagerDuty's own MCP server, where available, provides a PagerDuty-specific endpoint. Arcade adds per-user OAuth, approval workflows, response redaction, scope controls, and one MCP gateway that works across supported agent frameworks and clients.

Arcade agents can list, search, and inspect incidents, incident activity, services, teams, escalation policies, schedules, on-call entries, and users. They can also identify the connected user, reassign incidents, and acknowledge, resolve, close, or reopen incidents.

Arcade requests the PagerDuty OAuth permissions required by the actions you enable. Read-only incident and account lookups need read access; reassigning incidents or changing incident status needs the corresponding write permissions. Grant the narrowest access that supports your workflow.

Yes. Each user authorizes their own PagerDuty account through OAuth. Actions run under that user's authorization, so the agent can access only the PagerDuty data and write actions that user has approved.

Yes. Contextual Access policies can require human approval before consequential PagerDuty actions such as reassigning an incident or changing its status. The call proceeds only after the policy's conditions have been satisfied.

Arcade proxies PagerDuty API calls and does not persist your content as part of normal tool execution. OAuth credentials are brokered and stored encrypted at rest, and the model never receives them.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the user's PagerDuty authorization remains valid. If it is revoked, rotated, or can no longer be refreshed, calls stop until the user reconnects PagerDuty.

PagerDuty's API rate limits and any account or endpoint quotas still apply to calls made through Arcade. The available details do not specify a separate Arcade quota for these PagerDuty actions, so design polling and incident scans around PagerDuty's limits.

Ready to actually ship your agent?

Connect your agent to PagerDuty with managed OAuth, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the PagerDuty Quickstart