pagerduty-api.delete_team high conf mediumOBO
Destroys a team and its access boundary, severing associations to services, schedules, and escalation policies and disrupting who is responsible for incidents.
pagerduty-api.list_users high conf mediumhuman approval
Bulk-reads the account's user directory — names, email addresses, and contact methods — exposing personal data of every responder at once.
All other tools (19)
pagerduty-api.add_responders medium conf mediumaudit
Pages additional users into an active incident, notifying them and pulling them into the response.
pagerduty-api.add_team_member medium conf mediumaudit
Adds a user to a team, granting them the team's visibility and on-call scope; reversible but expands who can act on the team's services.
pagerduty-api.append_event_orchestration_router_rule medium conf mediumaudit
Adds a routing rule that changes which service catches matching events, altering alert delivery for the orchestration.
pagerduty-api.create_escalation_policy medium conf mediumaudit
Defines a new chain of who gets paged and when; a flawed policy leaves incidents without a responder.
pagerduty-api.create_incident medium conf mediumaudit
Opens a new incident that pages on-call responders and starts escalation timers for the target service.
pagerduty-api.create_schedule medium conf mediumaudit
Establishes a new on-call schedule that determines which responders are reachable during incidents.
pagerduty-api.create_schedule_override medium conf mediumaudit
Temporarily replaces who is on call for a window, redirecting pages to a different responder.
pagerduty-api.create_service medium conf mediumaudit
Registers a new service that events route to and incidents open against, defining a unit of monitored infrastructure.
pagerduty-api.create_status_page_post medium conf mediumaudit
Publishes a customer-facing status page post, a public statement about service health with direct reputational impact.
pagerduty-api.create_team medium conf mediumaudit
Creates a new team that acts as an access and ownership boundary for services, schedules, and escalation policies.
pagerduty-api.delete_webhook_subscription medium conf mediumaudit
Removes an event-delivery subscription, silently breaking downstream integrations and automation that depend on incident notifications.
pagerduty-api.get_responder_load_metrics low conf mediumallow
Surfaces per-responder on-call workload metrics tied to identifiable employees, personal data that can drive performance judgments about individuals.
pagerduty-api.manage_incidents medium conf mediumaudit
Bulk-changes incident status, urgency, assignment, or resolution, and can resolve active incidents or reassign responders across many records at once.
pagerduty-api.remove_team_member medium conf mediumaudit
Removes a user from a team, potentially stripping their on-call coverage and leaving gaps in incident response for the team's services.
pagerduty-api.start_incident_workflow medium conf mediumaudit
Triggers an automated incident-response workflow that can run notifications and downstream actions without further human review.
pagerduty-api.update_escalation_policy medium conf mediumaudit
Changes who is notified during an incident and in what order; a bad edit can silently route alerts away from the right responders.
pagerduty-api.update_event_orchestration_router medium conf mediumaudit
Rewrites how incoming events are routed to services; misconfiguration can silently drop or misdirect alerts so incidents go unpaged.
pagerduty-api.update_schedule medium conf mediumaudit
Alters on-call rotations; a mistaken change can leave hours with no responder assigned and incidents unattended.
pagerduty-api.update_service medium conf mediumaudit
Changes service configuration such as its escalation policy or alert grouping, affecting how incidents are triaged and routed.