Register a new route (URL path) in a UX app. [Write]
AI agents use create_ux_app_route 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.
Creating UX app routes modifies application configuration reversibly. While it doesn't delete data, it could redirect traffic, expose endpoints, or alter application behavior in ways that might be noticed and corrected. Impact is medium because misuse could disrupt application routing and user access, but the action is reversible—routes can be removed or reconfigured.
From the tool's definition Tool creates/registers new routes (URL paths) in a UX app. The description explicitly states "Register a new route" which is a creation action. The tag "[Write]" further confirms this is a write operation.
Attacks that exploit this kind of access
Register a new route (URL path) in a UX app. [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.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for create_ux_app_route: 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.
create_ux_app_route 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_app_route 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_app_route. 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_app_route 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →