64 tools from the PagerDuty MCP Server, categorised by risk level.
View the PagerDuty policy →get_alert_from_incident Retrieve a specific alert from an incident 2/5 get_alert_grouping_setting Retrieve a specific alert grouping setting 2/5 get_change_event Retrieve a specific change event 2/5 get_escalation_policy Retrieve a specific escalation policy 2/5 get_event_orchestration Retrieve a specific event orchestration 2/5 get_event_orchestration_global Get global orchestration configuration 2/5 get_event_orchestration_router Get router configuration for an orchestration 2/5 get_event_orchestration_service Get service orchestration configuration 2/5 get_incident Retrieve a specific incident 2/5 get_incident_workflow Retrieve a specific incident workflow 2/5 get_log_entry Retrieve a specific log entry 2/5 get_outlier_incident Retrieve outlier incident information 2/5 get_past_incidents Retrieve past incidents related to an incident 2/5 get_related_incidents Retrieve related incidents 2/5 get_schedule Retrieve a specific schedule 2/5 get_service Retrieve a specific service 2/5 get_status_page_post Retrieve a specific status page post 2/5 get_team Retrieve a specific team 2/5 get_user_data Get the current user data 2/5 list_alert_grouping_settings List alert grouping settings with filtering 2/5 list_alerts_from_incident List all alerts for an incident 2/5 list_change_events List change events with optional filtering 2/5 list_escalation_policies List escalation policies 2/5 list_event_orchestrations List event orchestrations 2/5 list_incident_change_events List change events for a specific incident 2/5 list_incident_notes List all notes for an incident 2/5 list_incident_workflows List incident workflows 2/5 list_incidents List incidents with filtering 2/5 list_log_entries List all log entries across the account 2/5 list_oncalls List on-call schedules 2/5 list_schedule_users List users in a schedule 2/5 list_schedules List schedules 2/5 list_service_change_events List change events for a specific service 2/5 list_services List services 2/5 list_status_page_impacts List impact levels for a status page 2/5 list_status_page_post_updates List updates for a status page post 2/5 list_status_page_severities List severity levels for a status page 2/5 list_status_page_statuses List available statuses for a status page 2/5 list_status_pages List all status pages 2/5 list_team_members List members of a team 2/5 list_teams List teams 2/5 list_users List users in the account 2/5 add_note_to_incident Add a note to an incident 3/5 add_responders Add responders to an incident 4/5 add_team_member Add a user to a team 4/5 append_event_orchestration_router_rule Add a routing rule to an orchestration 4/5 create_alert_grouping_setting Create a new alert grouping setting 4/5 create_incident Create a new incident 5/5 create_schedule Create a new on-call schedule 4/5 create_schedule_override Create an override for an on-call schedule 4/5 create_service Create a new service in PagerDuty 4/5 create_status_page_post Create a new status page post 4/5 create_status_page_post_update Add an update to a status page post 4/5 create_team Create a new team 3/5 manage_incidents Update incident status, urgency, or assignment 5/5 update_alert_grouping_setting Update an alert grouping setting 4/5 update_event_orchestration_router Update router config for an orchestration 5/5 update_schedule Update an existing on-call schedule 4/5 update_service Update an existing service 4/5 update_team Update an existing team 3/5 The PagerDuty MCP server exposes 64 tools across 4 categories: Read, Write, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the PagerDuty server.
PagerDuty tools are categorised as Read (42), Write (18), Destructive (3), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept