Get details of a specific PagerDuty incident.
AI agents call pagerduty_get_incident 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 and queries incident data from PagerDuty without creating, modifying, deleting, or executing any actions. It is a read-only operation with minimal blast radius if misused by an AI agent, as it only exposes existing incident information.
From the tool's definition Tool name is 'pagerduty_get_incident' and description states 'Get details of a specific PagerDuty incident' — the verb 'get' and lack of any modification language clearly indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get details of a specific PagerDuty incident. 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_get_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 Integrations MCP. Nothing to install.
pagerduty_get_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_get_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_get_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_get_incident 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 →