snow_scripted_rest_api
Invoke a Scripted REST API resource at /api/<namespace>/<path> with chosen method (GET/POST/PUT/PATCH/DELETE) and optional JSON body. Use for instance-defined REST endpoints; for stock table API use snow_custom_api.
This record as markdown: /tools/serac/snow-scripted-rest-api.md
What snow_scripted_rest_api does on Serac
AI agents invoke snow_scripted_rest_api 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_scripted_rest_api is rated High
This tool can invoke arbitrary scripted REST endpoints with any HTTP method including POST, PUT, PATCH, and DELETE. Since these are 'scripted' endpoints on a ServiceNow instance, they may execute custom server-side code with unpredictable side effects ranging from data modification to deletion.
From the tool's definition Invoke a Scripted REST API resource... with chosen method (GET/POST/PUT/PATCH/DELETE) and optional JSON body
Attacks that exploit this kind of access
The rule that runs snow_scripted_rest_api 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_scripted_rest_api, this is the rule to start with:
snow_scripted_rest_api 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_scripted_rest_api call is checked against it from then on.
Questions about snow_scripted_rest_api
Invoke a Scripted REST API resource at /api/<namespace>/<path> with chosen method (GET/POST/PUT/PATCH/DELETE) and optional JSON body. Use for instance-defined REST endpoints; for stock table API use snow_custom_api. 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_scripted_rest_api: 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_scripted_rest_api 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_scripted_rest_api 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_scripted_rest_api. 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_scripted_rest_api 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