This page describes AAES Govern’s controls. AAES Operate has private-work permissions, operational reviews and recorded-spend limits; it does not include Govern. About AAES Govern
Before you enable this package
The registered host is api.pagerduty.com for the US service region. EU accounts use api.eu.pagerduty.com; update endpoints, resource locators and allowlists together. Bind INCIDENT_ID before enabling updates.
Read each action's effects and exclusions below. Before installation, also read the complete package requirements, including credential issuance, scope, expiry, and provider permissions. These are deployment prerequisites, not capabilities this package supplies.
Capabilities (5)
Each capability below is one registered operation. The complete package JSON includes its exact network destination allowlist. The repository stores it at packs/pagerduty.json and embeds a copy in the release binary.
Risk tiers. R0 is the minimum for reads. R2 is the minimum for write, create, update, execute, and invoke. R3 is the minimum for delete, send, pay, deploy, approve, share, and transfer. Operators can raise these levels. A minimum tier does not measure the operation's business or confidentiality risk.
On supported execution paths routed through AAES Govern, the R3 actions listed below require approval by an authorized person. Bypass paths and observation-only registrations are outside that guarantee. A provider's restoration feature does not remove this approval requirement. A provider-side approval, such as approving a GitLab merge request, is also separate from AAES Govern human approval. The capability matrix shows which execution paths are implemented, restricted to lab use, or refused at startup. Live compatibility must be tested in your environment.
Field guide. Endpoint is the service address and request method. Connector is the adapter that makes the call. Custody describes how the credential is held; the credential reference identifies the value to resolve. Data class sets handling requirements: pii means personal data, financial means financial records, and internal means internal organizational data.
pagerduty.incidents.read v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
GET https://api.pagerduty.com/incidents- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-pagerduty-api-token- Data class
- pii
Read incidents.
List incidents: titles, statuses, urgency, service references and the assigned responders, whose names and emails are personal data. The registered path covers the collection read only — single-incident reads (GET /incidents/{id}), alerts and notes are not registered by this pack.
pagerduty.services.read v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
GET https://api.pagerduty.com/services- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-pagerduty-api-token- Data class
- internal
Read services.
List services: names, statuses, escalation policy and team references, which reveal internal service topology. The registered path covers the collection read only — single-service reads (GET /services/{id}) are not registered by this pack.
pagerduty.users.read v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
GET https://api.pagerduty.com/users- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-pagerduty-api-token- Data class
- pii
Read users.
List users of the account: names, emails, roles and time zones, which are personal data. The registered path covers the collection read only — single-user reads (GET /users/{id}), contact methods and notification rules are not registered by this pack.
pagerduty.oncalls.read v1.0.0R0
- Kind
- tool
- Action
- read
- Endpoint
GET https://api.pagerduty.com/oncalls- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-pagerduty-api-token- Data class
- pii
Read on-call schedules.
List on-call entries for a time range: which user is on call for which escalation policy and when — the embedded user objects (names, emails) are personal data, and the schedule itself reveals who can be woken. Collection read; there is no record variant registered.
pagerduty.incidents.update v1.0.0R3
- Kind
- tool
- Actions
- update, send
- Endpoint
PUT https://api.pagerduty.com/incidents/INCIDENT_ID- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-pagerduty-api-token- Data class
- pii
Update incidents.
Update one incident via PUT /incidents/{id}, which PagerDuty documents as the operation that acknowledges, resolves, escalates or reassigns an incident — the registered PUT cannot restrict the caller to a subset of those transitions. Acknowledging marks the incident as owned and takes it out of the escalation path; resolving closes it; escalating or reassigning notifies or wakes another responder.
Because the same call can page a human, the capability is registered as update and send at the minimum R3 tier, and send is one of the designated actions requiring human approval.
On supported execution paths mediated by AAES Govern, irreversible actions require approval by an authorized person; this does not prevent calls through bypass or observation-only paths. A notification already delivered cannot be recalled after delivery, and this pack claims no general reversibility for the state change either. PagerDuty's API schema marks a From header as required for this write — the email address of a valid user on the account — and the deployment must emit it alongside Authorization.
INCIDENT_ID is a placeholder the deployment substitutes with a concrete incident id before enabling.
Credential reference
The credential field names a reference rather than containing credential material. Packs are designed not to contain secrets; the format checks cover only known credential formats and cannot prove that arbitrary text contains no secrets. Installing a package registers its capabilities. Configure the provider credentials, endpoints, and network access, then test the integration in your environment before enabling it.
- Reference
secret-ref-pagerduty-api-token- Custody
- customer_vault
- Injection
- header (Authorization)
Configure the value and injection format specified in the package. Assign responsibility for credential rotation and revocation, restrict provider permissions, and keep credential material out of logs and responses.
Complete credential requirements
A PagerDuty REST API access token for the customer's own account, held in the client's own secret manager. The stored material must be the complete Authorization header value: the scheme 'Token', the literal parameter name 'token=', then the key — 'Token token=<API_KEY>' — exactly as PagerDuty's published API schema defines the security scheme.
A general access key inherits account-wide permissions and a user token key is restricted to the issuing user's own permissions, so issue the token at the least privilege that covers these reads and, where enabled, incident updates; a read-only general access key (a documented creation option that restricts the key to GET calls) covers the four reads only.
PagerDuty's published API schema marks the From header as required on the incident update PUT — the email address of a valid user associated with the account, the acting user recorded for the change; the deployment wiring the incident update capability must emit that From header alongside Authorization, and one that cannot must leave the write disabled.
PagerDuty REST API keys do not expire on their own, and PagerDuty documents two distinct controls for general access keys: disabling a key stops it working with the REST API but can be reversed by re-enabling it, while deleting a key permanently removes it; user token keys are deleted by their owner or an admin.
Restricting who can create keys does not invalidate keys already issued. Rotation therefore sits with an external deployment process: the executor injects the stored value verbatim and performs no token lifecycle of its own.
Executor hygiene: the value must live only in executor memory for the lifetime of a call, must never be written to logs, traces or diagnostics, and must not appear in crash dumps; a deployment that cannot meet that bar must not enable the pack.
Resources
pagerduty-incidents(api, pii):https://api.pagerduty.com/incidentspagerduty-services(api, internal):https://api.pagerduty.com/servicespagerduty-users(api, pii):https://api.pagerduty.com/userspagerduty-oncalls(api, pii):https://api.pagerduty.com/oncalls
Technical package and review record
Complete provider requirements and exclusions
The registered host 'api.pagerduty.com' is PagerDuty's real REST API host for the US service region — a shared SaaS authority, not a placeholder; accounts in the EU service region use the regional host api.eu.pagerduty.com, which the deployment substitutes into the endpoints, the resource locators and the egress allowlist together — the allowlist matches exactly, so all three must move as one. INCIDENT_ID in the incident-update path is a placeholder the deployment substitutes with a concrete incident id at registration time, before enabling.
Every read endpoint here is a collection read only: single-record reads (GET /incidents/{id}, GET /services/{id}, GET /users/{id}) are not registered.
Approval classification: the incident update capability is registered as update and send at the minimum R3 tier because the registered PUT performs every transition PagerDuty documents for it — acknowledge, resolve, escalate and reassign — and escalating or reassigning notifies or wakes another responder: send, one of the designated actions requiring human approval. The classification covers every effect the endpoint enables, including effects beyond the intended subset; the mass-manage variant PUT /incidents is not registered.
Documented exclusions — this pack does not register: incident creation (POST /incidents — declaring an incident notifies responders, a send-class effect), incident notes, alerts, any service, user, escalation-policy, schedule or team write, response plays, and the Events API (a separate host, events.pagerduty.com, that no capability here may reach).
Download the complete package JSON for exact network allowlists, credential requirements, exclusions, and setup notes. Read these requirements before installation.
The full documentation review record is supplied in the evaluation package. The evaluation package runs in your environment and comes only with the paid design partnership. This page reproduces the source links and review block; the full record is available for evaluation. Discuss a design partnership to inspect it before installation.
Review block
This section reproduces the review block recorded in the pack file. The evidence and approval record is separate: for a reviewed pack, it is in the evaluation materials and in the release binary's embedded assets.
Review completed: 2026-09-22
3 sources, retrieved 2026-09-21
- https://raw.githubusercontent.com/PagerDuty/api-schema/main/reference/REST/openapiv3.json (retrieved 2026-09-21)
- https://support.pagerduty.com/main/docs/api-access-keys (retrieved 2026-09-21)
- https://support.pagerduty.com/main/docs/service-regions (retrieved 2026-09-21)
Current documentation links are navigation aids. They do not change the package, its historical sources or its review date. Review dates describe a documentation review, not a live integration test. No package is provider-endorsed or yet tested against a live provider tenant.
Release identity
SHA-256 of the pack file bytes: 6cccdd20e3ff946abb771842635e437e77444999fb173bb28e5fd5e4d2309f78
Distributable: yes, digest matches the release manifest. Editing a package changes its release identity. A deployment plan checks its own file digests; it does not restore reviewed status or authenticate approval.