batch_request

What batch_request does on ServiceNow MCP Server

AI agents invoke batch_request to trigger actions in ServiceNow MCP Server. 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 batch_request is rated High

This tool executes arbitrary ServiceNow REST API operations without apparent constraints on operation type or target. While individual operations might be Read or Write, the ability to batch multiple heterogeneous operations creates an Execute-class risk—the effects depend entirely on which API calls are included. If a batch includes DELETE or destructive operations, this tool could cause irreversible harm at scale.

From the tool's definition Tool performs 'Execute multiple ServiceNow REST API operations in a single HTTP call.' REST API operations can include creates, updates, deletes, and other state-changing actions. The batch nature and multiplicity significantly expand potential blast radius.

The rule that runs batch_request safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For batch_request, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch_request": {
      "limits": [
        {
          "counter": "batch_request_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about batch_request