snow_create_security_incident
Create security incident with automated threat correlation and priority assignment
This record as markdown: /tools/serac/snow-create-security-incident.md
What snow_create_security_incident does on Serac
AI agents use snow_create_security_incident to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
Why snow_create_security_incident is rated Medium
This tool creates a new security incident record in ServiceNow, which is a reversible Write operation (incidents can be updated or deleted). However, creating false or spurious security incidents could trigger incident response workflows, alert fatigue, or divert security team resources, making misuse high-severity.
From the tool's definition Tool name contains 'create' and description states 'Create security incident' — this creates a new record in ServiceNow.
Attacks that exploit this kind of access
The rule that runs snow_create_security_incident safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_create_security_incident, this is the rule to start with:
snow_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 Serac, apply this rule, and every snow_create_security_incident call is checked against it from then on.
Questions about snow_create_security_incident
Create security incident with automated threat correlation and priority assignment. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_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 Serac. Nothing to install.
snow_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 snow_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 snow_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.
snow_create_security_incident is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
This server
Across the catalogue