Skip to main content

​
Overview

The get_escalation_policy tool retrieves detailed information about a specific escalation policy, including its escalation rules, targets, timing, and associated services and teams.
This is a read-only tool that does not modify any data in your PagerDuty account.

​
Parameters

​
policy_id
string
required
The unique identifier of the escalation policy to retrieve.Example: "P5DTI0W"

​
Response

Returns a detailed escalation policy object.
​
id
string
The unique identifier of the escalation policy
​
type
string
Always returns "escalation_policy"
​
summary
string
A short-form description of the escalation policy
​
name
string
The name of the escalation policy
​
description
string
The description of the escalation policy
​
escalation_rules
array
The ordered list of escalation rules for the policy. Each rule defines when and to whom an incident should escalate.
​
num_loops
integer
The number of times the escalation policy will repeat after reaching the end of its escalation. Set to 0 for no looping.
​
on_call_handoff_notifications
string
Determines how on-call handoff notifications will be sent. Options:
  • "if_has_services" - Send notifications only if the policy has services (default)
  • "always" - Always send handoff notifications
​
services
array
The services using this escalation policy
​
teams
array
The teams associated with this escalation policy
​
self_url
string
The API URL at which this escalation policy is accessible
​
html_url
string
The URL at which this escalation policy is accessible in the PagerDuty web UI
​
created_at
datetime
The date/time when this escalation policy was created
​
updated_at
datetime
The date/time when this escalation policy was last updated

​
Example Usage

"Show me the details of escalation policy P5DTI0W"

​
Use Cases

  • Review escalation flow - Examine how incidents progress through escalation levels
  • Verify escalation timing - Check delay settings between escalation levels
  • Audit escalation targets - See which users and schedules are involved in escalations
  • Understand policy loops - Determine if and how many times the policy repeats
  • Check service associations - View which services use this escalation policy

​
Response Example

{
  "id": "P5DTI0W",
  "type": "escalation_policy",
  "name": "Production Team Escalation",
  "description": "Primary escalation policy for production services",
  "escalation_rules": [
    {
      "id": "PJHF123",
      "escalation_delay_in_minutes": 30,
      "targets": [
        {
          "id": "PUSER1",
          "type": "user_reference",
          "summary": "John Doe"
        }
      ],
      "escalation_rule_assignment_strategy": "round_robin"
    }
  ],
  "num_loops": 2,
  "on_call_handoff_notifications": "if_has_services"
}

Build docs developers (and LLMs) love

Get started for freeTalk to us