pagerduty_resolve_incident
Resolve a PagerDuty incident by ID.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pagerduty-resolve-incident.md
What pagerduty_resolve_incident does on UnClick
AI agents use pagerduty_resolve_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 |
|---|---|---|---|
api_key | string | Yes | PagerDuty API key |
incident_id | string | Yes | Incident ID to resolve |
Parameters from the server's own tool schema.
Why pagerduty_resolve_incident is rated Medium
This tool updates an incident's status reversibly (incidents can be re-triggered or reopened), making it a Write action rather than Destructive. The impact is medium severity because resolving incidents can affect alerting workflows and on-call response cycles, but the action is not destructive and does not involve financial transactions. Confidence is high given the clear action description.
From the tool's definition 'Resolve a PagerDuty incident by ID' — the verb 'resolve' modifies the state of an incident record in PagerDuty, marking it as resolved.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs pagerduty_resolve_incident safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pagerduty_resolve_incident, this is the rule to start with:
pagerduty_resolve_incident stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every pagerduty_resolve_incident call is checked against it from then on.
Questions about pagerduty_resolve_incident
Resolve a PagerDuty incident by ID. 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_resolve_incident accepts 2 parameters: api_key, incident_id. Required: api_key, incident_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_resolve_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_resolve_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_resolve_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_resolve_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_resolve_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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue