Integrations/PagerDuty

Control what your AI agents do in PagerDuty.

Let your team build AI agents for PagerDuty. Bollard AI controls what each one can do, area by area.

Request early accessSee how it works →
PagerDuty
On-Call Agent
Incidents Account areaOffReadFull use
Services Account areaOffReadFull use
Escalation Policies Account areaOffReadFull use
Trigger alerts
What agents can do

Set what each agent can do across your account.

Each area of PagerDuty, like incidents, services, or escalation policies, gets one of three levels: Off, Read, or Full use. Anything not allowed is denied.

Off
No access
The agent can't see that part of your account.
Read
Read-only
The agent can read incidents and services in that area. It can't change anything.
Full use
Triage and update
The agent can acknowledge and update incidents in that area.

Some actions stay off until explicitly turned on

Each one pages people, or changes who gets paged and when, so it could override the limits set elsewhere.

Triggering alert eventsChanging escalation policiesDeleting services
Set up & manage

Connect once. Manage everyone from there.

Connect once, then control access person by person. No new keys to hand out.

Step 1 · Set up

Connect once, company-wide

An admin connects your company's PagerDuty a single time. Bollard AI lays out the areas of your account, and anything you don't allow stays out of reach for every agent.

Step 2 · Manage

Control access per person and agent

From one dashboard, set what every person and their agents can reach. Change it any time, with no new keys for anyone.

OffNo access
ReadRead-only
Full useRead, acknowledge, and update incidents in a single area
Example

An incident triage agent.

An on-call agent updates incidents and can read your services, but it can't trigger alerts or change escalation policies.

Incidents Account areaOffReadFull use
Services Account areaOffReadFull use
Escalation Policies Account areaOffReadFull use

Manage access

ALLOWEDOn-Call Agent updated an Incident
ALLOWEDOn-Call Agent read a Service
BLOCKEDOn-Call Agent tried to open Escalation Policies, denied by default

Monitor activity

The security model

Top-tier security.

Bollard AI is access control for AI agents. It sits between your agents and PagerDuty, so they never hold your PagerDuty keys and never reach PagerDuty directly.

Everything runs through Bollard AI

Agents send their requests to Bollard AI, not to PagerDuty. Bollard AI checks each one against your rules and passes only the allowed requests through.

Denied by default

Every area starts off-limits, and paging people is held back on top of that. An agent gets in only where you've allowed it, and anything Bollard AI doesn't recognise is refused and held for review, never waved through on a guess.

Your keys stay sealed

Your PagerDuty keys are sealed in a vault unique to your company and never shown again. Bollard AI unlocks them only for the instant an allowed request needs it.

Activity you can read

Every attempt is recorded in plain English: who or which agent, what they tried, which incident or service, and the decision. The record is readable and can't be edited after the fact.

Questions

PagerDuty, answered.

Does connecting PagerDuty hand Bollard AI your whole account?+
Only the areas you allow. An admin connects your PagerDuty, and you decide which areas, like incidents or services, each agent can reach. Bollard AI doesn't browse or copy your account. It sits in front of it and checks every request the agents make, passing or blocking each one.
Can an agent page people or change who gets paged?+
Not unless you turn it on. Triggering alert events and changing escalation policies are held off by default, so an agent can acknowledge and read incidents where you allow without ever paging people or changing who is on call, until you explicitly allow it.
Can an agent see more than the person who owns it?+
No. An agent reaches only what its owner reaches. An explicit Off always overrides an inherited permission.
Where do our PagerDuty keys live?+
Sealed in an encrypted vault, behind a key unique to your company. It's never shown again once connected, and Bollard AI unseals it only for the instant an allowed request needs it.
What happens when an agent tries something it's not allowed to do?+
Bollard AI blocks the request before it reaches PagerDuty, and the blocked attempt lands in the activity record with the reason.
How do we connect PagerDuty?+
An admin connects the company's PagerDuty once. Bollard AI seals the connection and lays out the areas of your account to set rules for. From then on, all management happens in the Bollard AI dashboard.
Early access

Put your team's agents to work in PagerDuty, without the risk.

We're onboarding our first development partners now. Tell us about your setup and we'll be in touch.

Request early accessAll integrations →