snow_switch_application_scope
Switch the current application scope for the OAuth service account by writing to sys_user_preference (name=sys_scope). All NEW artifacts created after the switch belong to that scope; existing artifacts stay in their original scope. Resolves the target by trying, in order: sys_id, scope name (e.g.
This record as markdown: /tools/serac/snow-switch-application-scope.md
What snow_switch_application_scope does on Serac
AI agents use snow_switch_application_scope 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_switch_application_scope is rated Medium
This tool writes to a system preference table (sys_user_preference), which modifies ServiceNow configuration state reversibly. While the scope switch itself is not destructive, it controls where subsequent artifacts are created and could lead to misplaced or unintended modifications in a target application scope.
From the tool's definition Tool description explicitly states 'writing to sys_user_preference (name=sys_scope)' and modifies the application scope for the OAuth service account, affecting which scope 'NEW artifacts created after the switch belong to'
Attacks that exploit this kind of access
The rule that runs snow_switch_application_scope 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_switch_application_scope, this is the rule to start with:
snow_switch_application_scope 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_switch_application_scope call is checked against it from then on.
Questions about snow_switch_application_scope
Switch the current application scope for the OAuth service account by writing to sys_user_preference (name=sys_scope). All NEW artifacts created after the switch belong to that scope; existing artifacts stay in their original scope. Resolves the target by trying, in order: sys_id, scope name (e.g. 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_switch_application_scope: 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_switch_application_scope 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_switch_application_scope 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_switch_application_scope. 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_switch_application_scope 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