snow_create_ux_experience · Serac MCP: Risk & Policy

WHAT IT DOES

What snow_create_ux_experience does on Serac

AI agents use snow_create_ux_experience 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_create_ux_experience needs a policy

This tool creates a new UX Experience object in ServiceNow, which is a reversible write operation. While it modifies the ServiceNow environment by adding a new experience, it does not execute arbitrary code, delete data, or commit financial transactions.

From the tool's definition Tool name contains 'create' and description explicitly states 'Create UX Experience' and 'Returns experienceID used by all subsequent workspace steps', indicating the tool creates and persists a new resource (a UX experience/workspace container) in ServiceNow.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

snow_create_ux_experience Rate-limited

snow_create_ux_experience 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_create_ux_experience": {
      "limits": [
        {
          "counter": "snow_create_ux_experience_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_create_ux_experience

What does the snow_create_ux_experience tool do? +

Create UX Experience via Builder Toolkit API - The top-level container for a workspace. Returns experienceID used by all subsequent workspace steps. 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_create_ux_experience? +

Register the Serac MCP server in PolicyLayer and add a rule for snow_create_ux_experience: 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_create_ux_experience? +

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

Can I rate-limit snow_create_ux_experience? +

Yes. Add a rate_limit block to the snow_create_ux_experience 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_create_ux_experience completely? +

Set action: deny in the PolicyLayer policy for snow_create_ux_experience. 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_create_ux_experience? +

snow_create_ux_experience 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.