New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

snow_sp_page_manage

Unified tool for ServiceNow Service Portal page lifecycle beyond creation: list, update, delete, clone, add_widget_instance. Wraps sp_page and sp_instance. Actions: - list — list sp_page rows, optionally filtered by portal id, public flag, or title fragment - update — patch sp_page fields (title,...

SERVERSerac SOURCEserac-labs/serac
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/serac/snow-sp-page-manage.md

What snow_sp_page_manage does on Serac

AI agents use snow_sp_page_manage 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_sp_page_manage is rated Medium

While the tool includes a destructive delete action, the primary design intent is page lifecycle management spanning create/update/clone operations. The delete action is noted to not cascade (limited scope). The majority of actions (list, update, clone, add_widget_instance) are reversible modifications.

From the tool's definition Tool performs multiple write/modification actions: 'update' patches sp_page fields, 'clone' duplicates pages, 'add_widget_instance' creates sp_instance rows. Also includes 'delete' which removes sp_page rows irreversibly.

Questions about snow_sp_page_manage

What does the snow_sp_page_manage tool do? +

Unified tool for ServiceNow Service Portal page lifecycle beyond creation: list, update, delete, clone, add_widget_instance. Wraps sp_page and sp_instance. Actions: - list — list sp_page rows, optionally filtered by portal id, public flag, or title fragment - update — patch sp_page fields (title, public, draft, css, internal) - delete — delete an sp_page row (does not cascade widget instances) - clone — duplicate an sp_page with a new id and title (optionally copying widget instances) - add_widget_instance — place an sp_widget on the page by creating an sp_instance row Use when: the agent needs to maintain Service Portal pages — renaming, retiring, duplicating layouts, or wiring widgets onto a page. For authoring a new sp_page, use snow_create_sp_page; for authoring a new sp_widget, use snow_create_sp_widget. Returns: sp_page rows with sys_id, id, title, public, draft; widget instance rows with sys_id, sp_widget reference, and column placement. 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.

How do I enforce a policy on snow_sp_page_manage? +

Register the Serac MCP server in PolicyLayer and add a rule for snow_sp_page_manage: 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.

What risk level is snow_sp_page_manage? +

snow_sp_page_manage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit snow_sp_page_manage? +

Yes. Add a rate_limit block to the snow_sp_page_manage 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.

How do I block snow_sp_page_manage completely? +

Set action: deny in the PolicyLayer policy for snow_sp_page_manage. 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.

What MCP server provides snow_sp_page_manage? +

snow_sp_page_manage 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Serac's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.