Creates a new, simple service request ticket (sc_request).
AI agents use create_request_ticket to create or update resources in Snow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Snow environment.
This tool creates a new record in ServiceNow's service catalog system but does not delete, destroy, or execute arbitrary operations. Service request creation is reversible (tickets can be cancelled or deleted), making it a Write operation rather than Destructive.
From the tool's definition Tool creates a new service request ticket (sc_request), which creates reversible data in ServiceNow. The description explicitly states 'Creates a new' service request, indicating data creation.
Documented attack patterns abuse exactly the kind of access create_request_ticket gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Snow, and nothing reaches the server without passing your rules. This is the rule we recommend for create_request_ticket:
{
"version": "1",
"default": "deny",
"tools": {
"create_request_ticket": {
"limits": [
{
"counter": "create_request_ticket_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_request_ticket 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.
Free to start. No card required.
Creates a new, simple service request ticket (sc_request). It is categorised as a Write tool in the Snow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Snow MCP server in PolicyLayer and add a rule for create_request_ticket: 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 Snow. Nothing to install.
create_request_ticket 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_request_ticket 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_request_ticket. 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_request_ticket is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Snow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
88 Snow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.