AI agents use pagerduty_create_incident to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
from | string | — | Email address of the user creating the incident (required by some accounts) |
title | string | Yes | Incident title/summary |
api_key | string | Yes | PagerDuty API key |
urgency | string | — | Urgency: high or low |
service_id | string | Yes | ID of the service to create the incident on |
body_details | string | — | Detailed description of the incident |
Parameters from the server's own tool schema.
Creating a PagerDuty incident is a Write operation that generates a new resource. However, it has high severity because it triggers notifications, wakes up on-call staff, and initiates incident response workflows. Misuse could cause alert fatigue, unnecessary escalations, or disrupt operations. It is not Destructive (reversible, incidents can be resolved) nor Financial.
From the tool's definition 'Create a new PagerDuty incident on a service' — creates a new incident record in PagerDuty, triggering alerts and escalations to on-call personnel
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Create a new PagerDuty incident on a service. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
pagerduty_create_incident accepts 6 parameters: from, title, api_key, urgency, service_id, body_details. Required: title, api_key, service_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for pagerduty_create_incident: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches UnClick. Nothing to install.
pagerduty_create_incident is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pagerduty_create_incident rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for pagerduty_create_incident. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
pagerduty_create_incident is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →