PagerDuty MCP Policy

GET STARTED

Download this policy scaffold and add your rules. Intercept enforces them on every tool call before it reaches PagerDuty.

terminal

# Download policy scaffold


curl -o pagerduty.yaml https://raw.githubusercontent.com/policylayer/intercept/main/policies/pagerduty.yaml

# Run with Intercept


intercept --policy pagerduty.yaml -- npx -y @pagerduty-mcp

Server documentation: https://github.com/PagerDuty/pagerduty-mcp-server

READ TOOLS

42

get_alert_grouping_setting Retrieve a specific alert grouping setting

list_alert_grouping_settings List alert grouping settings with filtering

get_change_event Retrieve a specific change event

list_change_events List change events with optional filtering

list_incident_change_events List change events for a specific incident

list_service_change_events List change events for a specific service

get_event_orchestration Retrieve a specific event orchestration

get_event_orchestration_global Get global orchestration configuration

get_event_orchestration_router Get router configuration for an orchestration

get_event_orchestration_service Get service orchestration configuration

list_event_orchestrations List event orchestrations

list_escalation_policies List escalation policies

get_escalation_policy Retrieve a specific escalation policy

get_alert_from_incident Retrieve a specific alert from an incident

get_incident Retrieve a specific incident

get_outlier_incident Retrieve outlier incident information

get_past_incidents Retrieve past incidents related to a specific incident

list_alerts_from_incident List all alerts for an incident

list_incident_notes List all notes for an incident

list_incidents List incidents

get_incident_workflow Retrieve a specific incident workflow

list_incident_workflows List incident workflows

get_log_entry Retrieve a specific log entry

list_log_entries List all log entries across the account

get_team Retrieve a specific team

list_team_members List members of a team

list_teams List teams

get_user_data Get the current user's data

list_users List users in the account

list_oncalls List on-call schedules

get_schedule Retrieve a specific schedule

list_schedule_users List users in a schedule

list_schedules List schedules

get_service Retrieve a specific service

list_services List services

get_status_page_post Retrieve a specific status page post

list_status_page_impacts List available impact levels for a status page

list_status_page_post_updates List updates for a status page post

list_status_page_severities List severity levels for a status page

list_status_page_statuses List available statuses for a status page

list_status_pages List all status pages

WRITE TOOLS

19

create_alert_grouping_setting Create a new alert grouping setting

update_alert_grouping_setting Update an alert grouping setting

update_event_orchestration_router Update router configuration for an orchestration

append_event_orchestration_router_rule Add a routing rule to an orchestration

add_note_to_incident Add a note to an incident

add_responders Add responders to an incident

create_incident Create a new incident

manage_incidents Update status, urgency, assignment, or escalation level

start_incident_workflow Start a workflow for an incident

add_team_member Add a user to a team

create_team Create a new team

update_team Update an existing team

create_schedule_override Create an override for a schedule

create_schedule Create a new on-call schedule

update_schedule Update an existing schedule

create_service Create a new service

update_service Update an existing service

create_status_page_post Create a new status page post

create_status_page_post_update Add an update to a status page post

DESTRUCTIVE TOOLS

3

delete_alert_grouping_setting Delete an alert grouping setting

delete_team Delete a team

remove_team_member Remove a user from a team

POLICY YAML

This scaffold lists every tool with empty rules. Add conditions — rate limits, argument validation, deny rules — then deploy with Intercept.

pagerduty.yaml

version: "1"
description: "Policy for pagerduty-mcp"
default: "allow"
tools:
    get_alert_grouping_setting:
        rules: []
    list_alert_grouping_settings:
        rules: []
    get_change_event:
        rules: []
    list_change_events:
        rules: []
    list_incident_change_events:
        rules: []
    list_service_change_events:
        rules: []
    get_event_orchestration:
        rules: []
    get_event_orchestration_global:
        rules: []
    get_event_orchestration_router:
        rules: []
    get_event_orchestration_service:
        rules: []
    list_event_orchestrations:
        rules: []
    list_escalation_policies:
        rules: []
    get_escalation_policy:
        rules: []
    get_alert_from_incident:
        rules: []
    get_incident:
        rules: []
    get_outlier_incident:
        rules: []
    get_past_incidents:
        rules: []
    get_related_incidents:
        rules: []
    list_alerts_from_incident:
        rules: []
    list_incident_notes:
        rules: []
    list_incidents:
        rules: []
    get_incident_workflow:
        rules: []
    list_incident_workflows:
        rules: []
    get_log_entry:
        rules: []
    list_log_entries:
        rules: []
    get_team:
        rules: []
    list_team_members:
        rules: []
    list_teams:
        rules: []
    get_user_data:
        rules: []
    list_users:
        rules: []
    list_oncalls:
        rules: []
    get_schedule:
        rules: []
    list_schedule_users:
        rules: []
    list_schedules:
        rules: []
    get_service:
        rules: []
    list_services:
        rules: []
    get_status_page_post:
        rules: []
    list_status_page_impacts:
        rules: []
    list_status_page_post_updates:
        rules: []
    list_status_page_severities:
        rules: []
    list_status_page_statuses:
        rules: []
    list_status_pages:
        rules: []
    create_alert_grouping_setting:
        rules: []
    update_alert_grouping_setting:
        rules: []
    update_event_orchestration_router:
        rules: []
    append_event_orchestration_router_rule:
        rules: []
    add_note_to_incident:
        rules: []
    add_responders:
        rules: []
    create_incident:
        rules: []
    manage_incidents:
        rules: []
    start_incident_workflow:
        rules: []
    add_team_member:
        rules: []
    create_team:
        rules: []
    update_team:
        rules: []
    create_schedule_override:
        rules: []
    create_schedule:
        rules: []
    update_schedule:
        rules: []
    create_service:
        rules: []
    update_service:
        rules: []
    create_status_page_post:
        rules: []
    create_status_page_post_update:
        rules: []
    delete_alert_grouping_setting:
        rules: []
    delete_team:
        rules: []
    remove_team_member:
        rules: []

FREQUENTLY ASKED QUESTIONS

What tools does the PagerDuty MCP server expose?

The PagerDuty MCP Server exposes 62 tools across 3 categories: Read, Write, Destructive. Each tool can be individually controlled with Intercept policies.

How do I enforce policies on PagerDuty?

Download the policy scaffold, add rules (rate limits, argument validation, deny rules), then run Intercept as a proxy in front of the PagerDuty MCP server. Every tool call is evaluated against your YAML policy before execution.

Is the PagerDuty policy free to use?

Yes. All Intercept policies are open source under the Apache 2.0 licence. Download, modify, and deploy without restrictions.

ENFORCE POLICIES ON PAGERDUTY

Open source. One binary. Zero dependencies.

VIEW ON GITHUB Browse all policies →