// MCP TOOL REFERENCE

PAGERDUTY TOOLS

64 tools from the PagerDuty MCP Server, categorised by risk level.

// ALL 64 PAGERDUTY TOOLS

READ 42 tools

Read get_alert_from_incident Retrieve a specific alert from an incident Read get_alert_grouping_setting Retrieve a specific alert grouping setting Read get_change_event Retrieve a specific change event Read get_escalation_policy Retrieve a specific escalation policy Read get_event_orchestration Retrieve a specific event orchestration Read get_event_orchestration_global Get global orchestration configuration Read get_event_orchestration_router Get router configuration for an orchestration Read get_event_orchestration_service Get service orchestration configuration Read get_incident Retrieve a specific incident Read get_incident_workflow Retrieve a specific incident workflow Read get_log_entry Retrieve a specific log entry Read get_outlier_incident Retrieve outlier incident information Read get_past_incidents Retrieve past incidents related to an incident Read get_related_incidents Retrieve related incidents Read get_schedule Retrieve a specific schedule Read get_service Retrieve a specific service Read get_status_page_post Retrieve a specific status page post Read get_team Retrieve a specific team Read get_user_data Get the current user data Read list_alert_grouping_settings List alert grouping settings with filtering Read list_alerts_from_incident List all alerts for an incident Read list_change_events List change events with optional filtering Read list_escalation_policies List escalation policies Read list_event_orchestrations List event orchestrations Read list_incident_change_events List change events for a specific incident Read list_incident_notes List all notes for an incident Read list_incident_workflows List incident workflows Read list_incidents List incidents with filtering Read list_log_entries List all log entries across the account Read list_oncalls List on-call schedules Read list_schedule_users List users in a schedule Read list_schedules List schedules Read list_service_change_events List change events for a specific service Read list_services List services Read list_status_page_impacts List impact levels for a status page Read list_status_page_post_updates List updates for a status page post Read list_status_page_severities List severity levels for a status page Read list_status_page_statuses List available statuses for a status page Read list_status_pages List all status pages Read list_team_members List members of a team Read list_teams List teams Read list_users List users in the account

WRITE 18 tools

Write add_note_to_incident Add a note to an incident Write add_responders Add responders to an incident Write add_team_member Add a user to a team Write append_event_orchestration_router_rule Add a routing rule to an orchestration Write create_alert_grouping_setting Create a new alert grouping setting Write create_incident Create a new incident Write create_schedule Create a new on-call schedule Write create_schedule_override Create an override for an on-call schedule Write create_service Create a new service in PagerDuty Write create_status_page_post Create a new status page post Write create_status_page_post_update Add an update to a status page post Write create_team Create a new team Write manage_incidents Update incident status, urgency, or assignment Write update_alert_grouping_setting Update an alert grouping setting Write update_event_orchestration_router Update router config for an orchestration Write update_schedule Update an existing on-call schedule Write update_service Update an existing service Write update_team Update an existing team

DESTRUCTIVE 3 tools

Destructive delete_alert_grouping_setting Delete an alert grouping setting Destructive delete_team Delete a team Destructive remove_team_member Remove a user from a team

EXECUTE 1 tools

Execute start_incident_workflow Start a workflow for an incident

// RUNNING THIS SERVER

The managed route: connect PagerDuty through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y @pagerduty-mcp

// FAQ

How many tools does the PagerDuty MCP server have? +

The PagerDuty MCP server exposes 64 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on PagerDuty tools? +

Route the PagerDuty server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do PagerDuty tools fall into? +

PagerDuty tools are categorised as Read (42), Write (18), Destructive (3), Execute (1). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.