create_security_incident
Create a Security Operations incident (requires WRITE_ENABLED=true)
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/create-security-incident.md
What create_security_incident does on NowAIKit — ServiceNow AI Toolkit
AI agents use create_security_incident to create or update resources in NowAIKit — ServiceNow AI Toolkit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NowAIKit — ServiceNow AI Toolkit environment.
Why create_security_incident is rated Medium
This tool creates new incident records in a security operations system, which is a reversible write operation. While the blast radius is significant (false or malicious security incidents could trigger incident response workflows, alert fatigue, or operational disruption), it does not permanently destroy data, move money, or execute arbitrary code.
From the tool's definition Tool name 'create_security_incident' and description 'Create a Security Operations incident' explicitly indicate creation of a new record. The note '(requires WRITE_ENABLED=true)' confirms it performs a write operation.
Attacks that exploit this kind of access
The rule that runs create_security_incident safely
PolicyLayer is an MCP gateway: it sits between your AI agents and NowAIKit — ServiceNow AI Toolkit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_security_incident, this is the rule to start with:
create_security_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 NowAIKit — ServiceNow AI Toolkit, apply this rule, and every create_security_incident call is checked against it from then on.
Questions about create_security_incident
Create a Security Operations incident (requires WRITE_ENABLED=true). It is categorised as a Write tool in the NowAIKit — ServiceNow AI Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NowAIKit — ServiceNow AI Toolkit MCP server in PolicyLayer and add a rule for create_security_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 NowAIKit — ServiceNow AI Toolkit. Nothing to install.
create_security_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_security_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_security_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_security_incident is provided by the NowAIKit — ServiceNow AI Toolkit MCP server (nowaikit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on NowAIKit — ServiceNow AI Toolkit, and thousands of servers like it.
This server
Across the catalogue