pagerduty_acknowledge_incident
Acknowledge a PagerDuty incident by ID.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pagerduty-acknowledge-incident.md
What pagerduty_acknowledge_incident does on UnClick
AI agents call pagerduty_acknowledge_incident to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | PagerDuty API key |
incident_id | string | Yes | Incident ID to acknowledge |
Parameters from the server's own tool schema.
Why pagerduty_acknowledge_incident is rated Low
Even though pagerduty_acknowledge_incident only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs pagerduty_acknowledge_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_acknowledge_incident, this is the rule to start with:
pagerduty_acknowledge_incident is read-only, so it stays allowed. 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_acknowledge_incident call is checked against it from then on.
Questions about pagerduty_acknowledge_incident
Acknowledge a PagerDuty incident by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
pagerduty_acknowledge_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_acknowledge_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_acknowledge_incident is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pagerduty_acknowledge_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_acknowledge_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_acknowledge_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