pagerduty_resolve_incident · UnClick MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

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 IT NEEDS A POLICY

Why pagerduty_resolve_incident needs a policy

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

Recommended rule Ready

Verdict

pagerduty_resolve_incident Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pagerduty_resolve_incident": {
      "limits": [
        {
          "counter": "pagerduty_resolve_incident_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches UnClick, so you can run agents against it safely.

FAQ

Questions about pagerduty_resolve_incident

What does the pagerduty_resolve_incident tool do? +

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.

What parameters does pagerduty_resolve_incident accept? +

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.

How do I enforce a policy on pagerduty_resolve_incident? +

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.

What risk level is pagerduty_resolve_incident? +

pagerduty_resolve_incident is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pagerduty_resolve_incident? +

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.

How do I block pagerduty_resolve_incident completely? +

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.

What MCP server provides pagerduty_resolve_incident? +

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.