pagerduty_list_incidents
AI agents call pagerduty_list_incidents to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries incident data from PagerDuty without causing side effects. The verb 'list' and context of sibling tools (airtable_list_records, amplitude_get_active_users) confirm this is a data retrieval operation. The empty description prevents full certainty, but the naming convention is consistent with read-only queries in similar MCP integrations.
From the tool's definition Tool name 'pagerduty_list_incidents' contains 'list', which retrieves/queries incident data without modification. The 'list' prefix is a strong indicator of read-only retrieval operations.
Attacks that exploit this kind of access
pagerduty_list_incidents. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations 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 Integrations MCP. 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 Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →