Create a new PagerDuty incident and page the on-call engineer.
AI agents use pagerduty_create_incident to create or update resources in PilotOps MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PilotOps MCP environment.
This tool creates a new incident record in PagerDuty and actively pages (notifies/alerts) an on-call engineer. While it is reversible in that incidents can be closed or updated, it has a high blast radius: triggering false or spurious pages disturbs on-call staff, can cause alert fatigue, and may initiate costly incident response workflows.
From the tool's definition Create a new PagerDuty incident and page the on-call engineer
Documented attack patterns abuse exactly the kind of access pagerduty_create_incident gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PilotOps MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for pagerduty_create_incident:
{
"version": "1",
"default": "deny",
"tools": {
"pagerduty_create_incident": {
"limits": [
{
"counter": "pagerduty_create_incident_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pagerduty_create_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.
Free to start. No card required.
Create a new PagerDuty incident and page the on-call engineer. It is categorised as a Write tool in the PilotOps MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PilotOps MCP server in PolicyLayer and add a rule for pagerduty_create_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 PilotOps MCP. Nothing to install.
pagerduty_create_incident is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pagerduty_create_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_create_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_create_incident is provided by the PilotOps MCP server (muhammedehab35/pilot_ops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PilotOps MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 PilotOps MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.