Update an existing UI Builder page. [Write]
AI agents use update_uib_page 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.
This tool modifies existing ServiceNow UI Builder pages, which are reversible changes that can affect application interface, user experience, and potentially organizational workflows. The high severity reflects that UI Builder pages often control critical user-facing interfaces and could impact many users if misconfigured by an AI agent. The '[Write]' tag in the description confirms the classification.
From the tool's definition Tool name 'update_uib_page' and explicit description 'Update an existing UI Builder page' with '[Write]' classification tag indicates modification of UI configuration data.
Attacks that exploit this kind of access
Update an existing UI Builder page. [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 update_uib_page: 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.
update_uib_page 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 update_uib_page 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 update_uib_page. 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.
update_uib_page 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 →