Get details of a specific UI Builder page including layout and child elements
AI agents call get_uib_page to retrieve information from ServiceNow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves UI Builder page metadata (layout, child elements) without modifying, executing, or deleting any data. It has no side effects beyond data retrieval, making it a Read operation. The blast radius is minimal—exposure of this tool to an AI agent poses no risk of data modification, code execution, or destructive actions.
From the tool's definition Tool name and description indicate a retrieval operation: 'Get details of a specific UI Builder page including layout and child elements'. The verb 'Get' and the absence of modification language confirm this is a query-only action.
Attacks that exploit this kind of access
Get details of a specific UI Builder page including layout and child elements. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for get_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.
get_uib_page is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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 →