snow_switch_application_scope · Serac MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why snow_switch_application_scope needs a policy

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

Recommended rule Ready

Verdict

snow_switch_application_scope Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "snow_switch_application_scope": {
      "limits": [
        {
          "counter": "snow_switch_application_scope_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Serac, so you can run agents against it safely.

FAQ

Questions about snow_switch_application_scope

What does the snow_switch_application_scope tool do? +

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.

How do I enforce a policy on snow_switch_application_scope? +

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.

What risk level is snow_switch_application_scope? +

snow_switch_application_scope is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit snow_switch_application_scope? +

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.

How do I block snow_switch_application_scope completely? +

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.

What MCP server provides snow_switch_application_scope? +

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.