snow_confirm_script_execution
⚡ Confirms and schedules script after user approval (use after snow_execute_script with requireConfirmation=true). Note: Uses same scheduled job approach.
This record as markdown: /tools/serac/snow-confirm-script-execution.md
What snow_confirm_script_execution does on Serac
AI agents invoke snow_confirm_script_execution to trigger actions in Serac. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why snow_confirm_script_execution is rated High
This tool executes arbitrary scripts on a ServiceNow instance via a scheduled job mechanism. Even though it requires prior user approval, the act of confirming and scheduling the script constitutes code execution with potentially unlimited blast radius — scripts can read, write, delete, or reconfigure any ServiceNow data or configuration.
From the tool's definition 'Confirms and schedules script after user approval' and 'Uses same scheduled job approach' — this tool triggers execution of a previously staged script on the ServiceNow platform.
Attacks that exploit this kind of access
The rule that runs snow_confirm_script_execution 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_confirm_script_execution, this is the rule to start with:
snow_confirm_script_execution stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_confirm_script_execution call is checked against it from then on.
Questions about snow_confirm_script_execution
⚡ Confirms and schedules script after user approval (use after snow_execute_script with requireConfirmation=true). Note: Uses same scheduled job approach. It is categorised as a Execute tool in the Serac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Serac MCP server in PolicyLayer and add a rule for snow_confirm_script_execution: 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_confirm_script_execution is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the snow_confirm_script_execution 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_confirm_script_execution. 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_confirm_script_execution 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