snow_create_ux_page_registry
STEP 4: Create Page Registry Record (sys_ux_page_registry) - Registers the page for use within the workspace configuration.
This record as markdown: /tools/serac/snow-create-ux-page-registry.md
What snow_create_ux_page_registry does on Serac
AI agents use snow_create_ux_page_registry to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
Why snow_create_ux_page_registry is rated Medium
This tool creates and registers a page registry record in ServiceNow, which modifies system configuration. While it creates data, it is reversible (records can be updated or deleted later). The blast radius is moderate—misuse could create unwanted UI pages or workspace configurations that clutter the system or mislead users, but does not directly delete data or execute arbitrary code.
From the tool's definition Tool name 'snow_create_ux_page_registry' and description 'Create Page Registry Record' and 'Registers the page' indicate creation of a new ServiceNow configuration record.
Attacks that exploit this kind of access
The rule that runs snow_create_ux_page_registry safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_create_ux_page_registry, this is the rule to start with:
snow_create_ux_page_registry 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 Serac, apply this rule, and every snow_create_ux_page_registry call is checked against it from then on.
Questions about snow_create_ux_page_registry
STEP 4: Create Page Registry Record (sys_ux_page_registry) - Registers the page for use within the workspace configuration. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_create_ux_page_registry: 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 Serac. Nothing to install.
snow_create_ux_page_registry 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 snow_create_ux_page_registry 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 snow_create_ux_page_registry. 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.
snow_create_ux_page_registry is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
This server
Across the catalogue