create_ux_experience · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What create_ux_experience does on ServiceNow-MCP

AI agents use create_ux_experience to create or update resources in ServiceNow-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.

WHY IT NEEDS A POLICY

Why create_ux_experience needs a policy

This tool creates new UX Experience configurations, which are reversible modifications to ServiceNow. The blast radius is medium because misconfigured app shells could affect user experience or expose unintended functionality, but the action is not destructive (can be deleted/modified) and does not move money or execute arbitrary code.

From the tool's definition Tool name 'create_ux_experience' and description states 'Create a new UX Experience (app shell) configuration', explicitly labeled **[Write]**. Creates new configuration objects in ServiceNow.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_ux_experience Rate-limited

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": {
    "create_ux_experience": {
      "limits": [
        {
          "counter": "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 ServiceNow-MCP, so you can run agents against it safely.

FAQ

Questions about create_ux_experience

What does the create_ux_experience tool do? +

Create a new UX Experience (app shell) configuration. [Write]. It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_ux_experience? +

Register the ServiceNow- MCP server in PolicyLayer and add a rule for 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 ServiceNow-MCP. Nothing to install.

What risk level is create_ux_experience? +

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 create_ux_experience? +

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

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

create_ux_experience is provided by the ServiceNow- MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.