snow_batch_request
Send multiple REST calls in a single round-trip via /api/now/v1/batch. Each entry has method, url, and body — replies come back in order under a generated batch ID. Cuts overhead when issuing many small operations.
This record as markdown: /tools/serac/snow-batch-request.md
What snow_batch_request does on Serac
AI agents invoke snow_batch_request 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_batch_request is rated High
This tool executes arbitrary batched REST API calls with configurable method, URL, and body. Since the batch can include any HTTP method (POST, PUT, DELETE, PATCH, etc.), it can perform Write, Destructive, or Execute operations depending on arguments. The most severe applicable category is Execute, as it triggers external operations whose effects depend entirely on what methods and endpoints are supplied.
From the tool's definition Send multiple REST calls in a single round-trip... Each entry has method, url, and body
Attacks that exploit this kind of access
The rule that runs snow_batch_request 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_batch_request, this is the rule to start with:
snow_batch_request 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_batch_request call is checked against it from then on.
Questions about snow_batch_request
Send multiple REST calls in a single round-trip via /api/now/v1/batch. Each entry has method, url, and body — replies come back in order under a generated batch ID. Cuts overhead when issuing many small operations. 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_batch_request: 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_batch_request 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_batch_request 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_batch_request. 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_batch_request 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