create_ux_experience
Create a new UX Experience (app shell) configuration. [Write]
This record as markdown: /tools/servicenow-mcp-server/create-ux-experience.md
What create_ux_experience does on ServiceNow MCP Server
AI agents use create_ux_experience to create or update resources in ServiceNow MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.
Why create_ux_experience is rated Medium
This tool creates a new configuration artifact (UX Experience/app shell) in ServiceNow, which modifies the state of the system reversibly. It does not delete data, execute arbitrary code, or move funds. While creating configurations could have wide blast radius if misused by an AI agent to create malicious app shells, the operation itself is not irreversible (configurations can be deleted or modified).
From the tool's definition Tool name is 'create_ux_experience' and description states 'Create a new UX Experience (app shell) configuration.' The **[Write]** tag in the description explicitly categorizes it as a write operation.
Attacks that exploit this kind of access
The rule that runs create_ux_experience safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_ux_experience, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every create_ux_experience call is checked against it from then on.
Questions about create_ux_experience
Create a new UX Experience (app shell) configuration. [Write]. It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP Server 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 Server. Nothing to install.
create_ux_experience 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 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.
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.
create_ux_experience is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue