This record as markdown: /tools/com-local-mcp-local-mcp/servicenow-create-incident.md
What servicenow_create_incident does on Local
AI agents use servicenow_create_incident to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
urgency | string | — | 1=Critical, 2=High, 3=Medium (default), 4=Low |
category | string | — | Incident category, e.g. 'software', 'hardware', 'network' |
description | string | — | Full description of the issue |
short_description | string | Yes | Brief summary of the issue (required) |
Parameters from the server's own tool schema.
Why servicenow_create_incident is rated Medium
This tool creates a new record in ServiceNow, which is a write operation that modifies system state reversibly. The blast radius is medium because unauthorized incident creation could lead to operational disruption, false alerts, or cluttered ticketing systems, but the action is reversible (incidents can be deleted or marked as invalid).
From the tool's definition Tool name is 'servicenow_create_incident' and description states 'Create a new incident in ServiceNow.' The verb 'create' and the action of adding a new incident record indicate data creation.
Attacks that exploit this kind of access
The rule that runs servicenow_create_incident safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For servicenow_create_incident, this is the rule to start with:
servicenow_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 Local, apply this rule, and every servicenow_create_incident call is checked against it from then on.
Questions about servicenow_create_incident
Create a new incident in ServiceNow. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
servicenow_create_incident accepts 4 parameters: urgency, category, description, short_description. Required: short_description. The full parameter table on this page comes from the server's own tool schema.
Register the Local 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 Local. 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 Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue