Delete a UI Builder page. [Write]
AI agents call delete_uib_page to permanently remove resources in ServiceNow-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of UI Builder pages cannot be undone and represents permanent loss of custom interface configurations. While not as critical as data loss affecting operations, it is destructive in nature and warrants a 'Destructive' classification rather than 'Write'. Severity is high because unauthorized deletion of application pages could impact user workflows and require recovery from backups.
From the tool's definition delete_uib_page deletes a UI Builder page, which is an irreversible removal of data/configuration. The tool name explicitly contains 'delete' and the description confirms it performs a deletion operation.
Attacks that exploit this kind of access
Delete a UI Builder page. [Write]. It is categorised as a Destructive tool in the ServiceNow-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for delete_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.
delete_uib_page is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →