Update multiple records across one or more ServiceNow tables in a single batch.
AI agents use batch_update_records to create or update resources in Now Sdk Ext — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Now Sdk Ext environment.
This tool modifies existing data (Write category) rather than creating new records or destructively deleting them. However, the ability to batch-update multiple records across multiple tables carries significant blast radius if an AI agent misuses it—an agent could inadvertently update critical business data at scale. This justifies 'high' severity rather than 'medium'.
From the tool's definition Tool description states 'Update multiple records across one or more ServiceNow tables in a single batch.' The verb 'update' and the capability to modify multiple records simultaneously indicate data modification without permanent deletion.
Documented attack patterns abuse exactly the kind of access batch_update_records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Now Sdk Ext, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_update_records:
{
"version": "1",
"default": "deny",
"tools": {
"batch_update_records": {
"limits": [
{
"counter": "batch_update_records_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch_update_records stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update multiple records across one or more ServiceNow tables in a single batch. It is categorised as a Write tool in the Now Sdk Ext MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Now Sdk Ext MCP server in PolicyLayer and add a rule for batch_update_records: 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 Now Sdk Ext. Nothing to install.
batch_update_records is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the batch_update_records 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 batch_update_records. 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.
batch_update_records is provided by the Now Sdk Ext MCP server (sonisoft-cnanda/now-sdk-ext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Now Sdk Ext, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
86 Now Sdk Ext tools catalogued and risk-classified — across an index of 43,000+ MCP servers.