snow_redeploy_script_endpoint
Force-redeploy the Serac scripted REST executor endpoint (/api/snow_flow_exec/execute). Use when snow_execute_script / UI policy tools fail with
This record as markdown: /tools/serac/snow-redeploy-script-endpoint.md
What snow_redeploy_script_endpoint does on Serac
AI agents invoke snow_redeploy_script_endpoint 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_redeploy_script_endpoint is rated High
This tool redeplooys a REST endpoint designed for executing scripts (/api/snow_flow_exec/execute), making it an Execute-category action. The ability to force-redeploy a code execution infrastructure component in ServiceNow poses critical risk: an AI agent could redeploy a compromised or malicious executor, bypass security controls, or cause widespread service disruption across the enterprise platform.
From the tool's definition "Force-redeploy the Serac scripted REST executor endpoint (/api/snow_flow_exec/execute). Use when snow_execute_script / UI policy tools fail with" — explicitly redeploys a script execution endpoint that permits arbitrary code execution.
Attacks that exploit this kind of access
The rule that runs snow_redeploy_script_endpoint 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_redeploy_script_endpoint, this is the rule to start with:
snow_redeploy_script_endpoint 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_redeploy_script_endpoint call is checked against it from then on.
Questions about snow_redeploy_script_endpoint
Force-redeploy the Serac scripted REST executor endpoint (/api/snow_flow_exec/execute). Use when snow_execute_script / UI policy tools fail with. 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_redeploy_script_endpoint: 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_redeploy_script_endpoint 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_redeploy_script_endpoint 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_redeploy_script_endpoint. 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_redeploy_script_endpoint 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