snow_create_application
Create a scoped application (sys_app), optionally bootstrapping an Update Set and switching the OAuth service account into the new scope so subsequent artifacts are tracked there. Use when: building a complete feature set (HR Portal, Customer Onboarding), bundling functionality for single-unit de...
This record as markdown: /tools/serac/snow-create-application.md
What snow_create_application does on Serac
AI agents use snow_create_application 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_application is rated Medium
This tool creates new structural elements (applications and update sets) within ServiceNow, modifying the instance's application architecture. While creations are theoretically reversible (the app could be deleted), the blast radius is high because: (1) it alters OAuth service account scope which affects subsequent system behavior; (2) it bootstraps update sets that track changes across the instance; (3) it creates…
From the tool's definition Tool creates a scoped application (sys_app) and optionally bootstraps an Update Set and switches OAuth service account scope.
Attacks that exploit this kind of access
The rule that runs snow_create_application 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_application, this is the rule to start with:
snow_create_application 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_application call is checked against it from then on.
Questions about snow_create_application
Create a scoped application (sys_app), optionally bootstrapping an Update Set and switching the OAuth service account into the new scope so subsequent artifacts are tracked there. Use when: building a complete feature set (HR Portal, Customer Onboarding), bundling functionality for single-unit deployment, building external integrations, or developing for multiple instances. Prefer global scope for small fixes, shared utilities, quick POCs, or cross-application work. Defaults: - auto_create_update_set=true — creates a fresh Update Set in the new app scope - auto_switch_scope=true — switches the OAuth service account to the new scope so subsequent artifacts track there Set either to false for manual control. 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_application: 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_application 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_application 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_application. 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_application 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