servicenow_bulk_update · Servicenow MCP: Risk & Policy

WHAT IT DOES

What servicenow_bulk_update does on Servicenow

AI agents use servicenow_bulk_update to create or update resources in Servicenow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Servicenow environment.

WHY IT NEEDS A POLICY

Why servicenow_bulk_update needs a policy

This tool creates or modifies data reversibly (Write category), not destructively. While it operates on multiple records simultaneously, the dry-run safeguard and ability to preview before committing mean changes are not irreversible. However, bulk operations affecting multiple records warrant 'high' severity due to the potential blast radius if an AI agent misapplies the query filter and modifies unintended records.

From the tool's definition Tool performs 'Update multiple records' operation. Description states it modifies records matching a query. The term 'bulk_update' indicates reversible modification of data at scale across a table.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

servicenow_bulk_update Rate-limited

servicenow_bulk_update 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "servicenow_bulk_update": {
      "limits": [
        {
          "counter": "servicenow_bulk_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Servicenow, so you can run agents against it safely.

FAQ

Questions about servicenow_bulk_update

What does the servicenow_bulk_update tool do? +

Update multiple records matching a query. Dry-run by default — always preview before committing. Args: - table (string): Target table (e.g., incident, change_request) - query (string): Encoded query to select records (e.g.,. It is categorised as a Write tool in the Servicenow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on servicenow_bulk_update? +

Register the Servicenow MCP server in PolicyLayer and add a rule for servicenow_bulk_update: 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 Servicenow. Nothing to install.

What risk level is servicenow_bulk_update? +

servicenow_bulk_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit servicenow_bulk_update? +

Yes. Add a rate_limit block to the servicenow_bulk_update 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.

How do I block servicenow_bulk_update completely? +

Set action: deny in the PolicyLayer policy for servicenow_bulk_update. 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.

What MCP server provides servicenow_bulk_update? +

servicenow_bulk_update is provided by the Servicenow MCP server (kylburns89/servicenow-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.