create_incident
Create a new incident record (requires WRITE_ENABLED=true)
This record as markdown: /tools/servicenow-mcp-server/create-incident.md
What create_incident does on ServiceNow MCP Server
AI agents use create_incident to create or update resources in ServiceNow MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.
Why create_incident is rated Medium
This tool creates new incident records in ServiceNow, a change that is reversible (incidents can be modified or closed). It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or perform only reads (Read).
From the tool's definition Tool name 'create_incident' and description 'Create a new incident record' explicitly indicate data creation. The requirement flag 'WRITE_ENABLED=true' confirms this is a write operation.
Attacks that exploit this kind of access
The rule that runs create_incident safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_incident, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every create_incident call is checked against it from then on.
Questions about create_incident
Create a new incident record (requires WRITE_ENABLED=true). It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP Server 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 Server. Nothing to install.
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 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 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.
create_incident is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue