create_incident · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What create_incident does on ServiceNow-MCP

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

WHY IT NEEDS A POLICY

Why create_incident needs a policy

This tool creates new data (incident records) in ServiceNow, which is a Write operation. It is reversible—incidents can be modified or deleted afterward. Severity is medium because creating false or spam incidents could disrupt service management workflows and cause operational noise, but the impact is bounded to incident management and doesn't affect financial systems, destroy data, or execute arbitrary code.

From the tool's definition Tool name is 'create_incident' and description states 'Create a new incident record'; the WRITE_ENABLED flag indicates this is a reversible creation operation, not a destructive action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_incident Rate-limited

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": {
    "create_incident": {
      "limits": [
        {
          "counter": "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 ServiceNow-MCP, so you can run agents against it safely.

FAQ

Questions about create_incident

What does the create_incident tool do? +

Create a new incident record (requires WRITE_ENABLED=true). It is categorised as a Write tool in the ServiceNow-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 create_incident? +

Register the ServiceNow- MCP server in PolicyLayer and add a rule for 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 ServiceNow-MCP. Nothing to install.

What risk level is create_incident? +

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

Can I rate-limit create_incident? +

Yes. Add a rate_limit block to the 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 create_incident completely? +

Set action: deny in the PolicyLayer policy for 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 create_incident? +

create_incident is provided by the ServiceNow- MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.