snow_create_hr_case
Open an HR Service Delivery case on sn_hr_core_case for a given HR service, with subject, opened_for (employee), and optional priority. Use this for HR tickets; for IT incidents use snow_create_incident.
This record as markdown: /tools/serac/snow-create-hr-case.md
What snow_create_hr_case does on Serac
AI agents use snow_create_hr_case 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_hr_case is rated Medium
This tool creates a new record (HR case) in ServiceNow, which is a reversible write operation. The case can be modified or deleted afterward. While creating HR cases could have business impact (e.g., initiating leave requests, benefits inquiries), it is not inherently destructive or financial in nature.
From the tool's definition Tool creates a new HR Service Delivery case via 'snow_create_hr_core_case' with parameters including subject, opened_for (employee), and priority. The verb 'Open' and 'create' indicate data creation.
Attacks that exploit this kind of access
The rule that runs snow_create_hr_case 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_hr_case, this is the rule to start with:
snow_create_hr_case 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_hr_case call is checked against it from then on.
Questions about snow_create_hr_case
Open an HR Service Delivery case on sn_hr_core_case for a given HR service, with subject, opened_for (employee), and optional priority. Use this for HR tickets; for IT incidents use snow_create_incident. 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_hr_case: 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_hr_case 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_hr_case 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_hr_case. 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_hr_case 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