PagerDuty logo

PagerDuty

Generally Available

With OAuth2 authorization, an agent can list and inspect incidents, look up on-call schedules and escalation policies, and help drive response workflows.

  • Incident Response
  • On-Call
  • Operations
Authentication
OAuth 2.0
Hosting
Vendor-hosted endpoint
Required scopes
3
Data actions
Read and write

How it works

Every agent request passes through Ferentin policy before it reaches PagerDuty.

  1. AI agentAsks for something
  2. Ferentin policies
    • OAuth 2.0 consent
    • Granular scope selection
    • Audit logging
  3. PagerDuty MCP serverAuthorized connection
  4. Governed resultMasked, logged, returned

What you can do with PagerDuty

  • List incidents
  • Read oncall schedules
  • Inspect services
  • Manage escalations

Permissions requested

The OAuth 2.0 scopes PagerDuty asks you to approve when you connect.

ScopeAccess
openidNot rated
readRead
writeElevated

Before you connect

  • Tools are read-only by default; the 'write' scope enables incident acknowledge/resolve, schedule edits, and other mutations. Drop 'write' from the scopes for a read-only connection.
  • Covers ~55 tools across incidents, services, teams, users, on-call schedules, escalation policies, event orchestrations, status pages, change events, and more.
  • OAuth supports PKCE (S256) and refresh tokens. The same auth model as the PagerDuty REST API applies.
  • The tool catalog populates on first live connection (tools/list against the upstream).

About PagerDuty

PagerDuty is an incident response platform for alerting, on-call scheduling, escalation, and coordinating resolution of operational disruptions.

Frequently asked about PagerDuty

What can AI agents do with PagerDuty through Ferentin?
Through Ferentin, agents can use PagerDuty for list incidents, read oncall schedules, inspect services and manage escalations. Every call is checked against your Ferentin policies first.
How is PagerDuty access secured?
Requests through the PagerDuty integration are covered by OAuth 2.0 consent, granular scope selection and audit logging. These controls are applied by Ferentin, not by PagerDuty, so they hold across every connected agent.
What permissions does the PagerDuty integration require?
The PagerDuty integration requests 3 OAuth 2.0 scopes: openid; read (read access); write (elevated access)
How do I connect PagerDuty to Ferentin?
Open the Ferentin admin console, add PagerDuty as a new connection and authenticate with OAuth 2.0. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.
Is the PagerDuty integration generally available?
Yes. The PagerDuty integration is generally available on Ferentin, including the free tier.