pagerduty_create_incident · Integrations MCP: Risk & Policy

WHAT IT DOES

What pagerduty_create_incident does on Integrations MCP

AI agents use pagerduty_create_incident to create or update resources in Integrations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.

WHY IT NEEDS A POLICY

Why pagerduty_create_incident needs a policy

Creating a PagerDuty incident triggers alerts and pages on-call responders, which is a Write operation (creates a new incident record) with significant real-world impact — it can wake people up and initiate incident response workflows. The empty description lowers confidence, but the naming convention 'create_incident' strongly implies creating a new resource.

From the tool's definition Tool name: pagerduty_create_incident — description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pagerduty_create_incident Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pagerduty_create_incident": {
      "limits": [
        {
          "counter": "pagerduty_create_incident_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Integrations MCP, so you can run agents against it safely.

FAQ

Questions about pagerduty_create_incident

What does the pagerduty_create_incident tool do? +

pagerduty_create_incident. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pagerduty_create_incident? +

Register the Integrations 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 Integrations MCP. Nothing to install.

What risk level is pagerduty_create_incident? +

pagerduty_create_incident is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pagerduty_create_incident? +

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.

How do I block pagerduty_create_incident completely? +

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.

What MCP server provides pagerduty_create_incident? +

pagerduty_create_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.