Create a new ServiceNow incident. Args: - short_description (string): One-line summary (required) - description (string): Detailed description - caller_id (string): sys_id or username of the caller/requester - category (string): Category (e.g.,
AI agents use servicenow_create_incident to create or update resources in Servicenow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Servicenow environment.
This tool creates new incident records in ServiceNow, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. The severity is medium because incident creation can trigger downstream workflows and notifications, but the operation itself is reversible (incidents can be closed or deleted). Confidence is high as the intent is unambiguous from the name and description.
From the tool's definition Tool name 'servicenow_create_incident' and description 'Create a new ServiceNow incident' indicate data creation. Args include 'short_description', 'description', 'caller_id', and 'category' which are typical incident record fields being populated.
Attacks that exploit this kind of access
Create a new ServiceNow incident. Args: - short_description (string): One-line summary (required) - description (string): Detailed description - caller_id (string): sys_id or username of the caller/requester - category (string): Category (e.g.,. It is categorised as a Write tool in the Servicenow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Servicenow MCP server in PolicyLayer and add a rule for servicenow_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. Nothing to install.
servicenow_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 servicenow_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 servicenow_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.
servicenow_create_incident is provided by the Servicenow MCP server (kylburns89/servicenow-mcp-server). 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 →