Unified tool for ServiceNow dashboard lifecycle beyond creation: list, get, share, embed, tab_create, tab_list. Wraps sys_dashboard, sys_dashboard_admin, and pa_tabs. Actions: - list — list sys_dashboard rows, optionally filtered by owner or active flag - get — retrieve a dashboard by sys_id or t...
AI agents use snow_dashboard_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.
While this tool includes read-only operations (list, get, embed), it also includes tab_create and share actions that create or modify dashboard configuration and access controls in ServiceNow. These are reversible changes (tabs can be deleted, sharing can be revoked), so it falls under Write rather than Execute or Destructive.
From the tool's definition Tool performs reversible create and modify operations: 'tab_create — create a pa_tabs row', 'share — share a dashboard with a user or group through sys_dashboard_admin'.
Attacks that exploit this kind of access
Unified tool for ServiceNow dashboard lifecycle beyond creation: list, get, share, embed, tab_create, tab_list. Wraps sys_dashboard, sys_dashboard_admin, and pa_tabs. Actions: - list — list sys_dashboard rows, optionally filtered by owner or active flag - get — retrieve a dashboard by sys_id or title (includes tab and widget counts) - share — share a dashboard with a user or group through sys_dashboard_admin - embed — produce an embed URL and iframe snippet for a dashboard (no write to ServiceNow) - tab_create — create a pa_tabs row attached to a dashboard - tab_list — list pa_tabs rows attached to a dashboard Use when: the agent needs to manage dashboards after they exist — sharing them, embedding them in a portal page, or organising their tab layout. For authoring a new dashboard, use snow_create_dashboard; for attaching widgets to it, use snow_add_dashboard_widget. Returns: dashboard records with sys_id, title, columns, active; share rows with user_or_group references; tab rows with order and title. 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_dashboard_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.
snow_dashboard_manage 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_dashboard_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.
Set action: deny in the PolicyLayer policy for snow_dashboard_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.
snow_dashboard_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.
snow_dashboard_manage is one line of Serac's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →