pagerduty_list_incidents
List PagerDuty incidents. Filter by status (triggered, acknowledged, resolved), service, or date range.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pagerduty-list-incidents.md
What pagerduty_list_incidents does on UnClick
AI agents call pagerduty_list_incidents 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 |
|---|---|---|---|
limit | number | — | Max results (default 25, max 100) |
offset | number | — | Pagination offset |
status | string | — | Filter by status: triggered, acknowledged, or resolved |
api_key | string | Yes | PagerDuty API key |
service_ids | string | — | Filter by service ID |
Parameters from the server's own tool schema.
Why pagerduty_list_incidents is rated Low
This tool retrieves and queries incident data from PagerDuty without creating, modifying, or deleting records. It is a read-only operation that filters existing data. Severity is medium because incident data may contain sensitive operational information about system outages and their timing, which could be valuable for reconnaissance or planning attacks, but the tool itself performs no destructive or harmful action.
From the tool's definition Tool name and description both indicate a list/retrieval operation: 'List PagerDuty incidents' with filtering capabilities by status, service, or date range. No modification, deletion, or execution of external operations is mentioned.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs pagerduty_list_incidents 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_list_incidents, this is the rule to start with:
pagerduty_list_incidents 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_list_incidents call is checked against it from then on.
Questions about pagerduty_list_incidents
List PagerDuty incidents. Filter by status (triggered, acknowledged, resolved), service, or date range. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
pagerduty_list_incidents accepts 5 parameters: limit, offset, status, api_key, service_ids. Required: api_key. 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_list_incidents: 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_list_incidents 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_list_incidents 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_list_incidents. 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_list_incidents 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