table_update · ServiceNow MCP Server MCP: Risk & Policy

WHAT IT DOES

What table_update does on ServiceNow MCP Server

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

WHY IT NEEDS A POLICY

Why table_update needs a policy

This tool creates or modifies data reversibly by updating records. While it does not delete data (which would be Destructive), it can modify critical ITSM records such as incidents, changes, or assets across any table with potentially wide blast radius if an AI agent applies incorrect updates to production systems.

From the tool's definition Tool name is 'table_update' and description states 'Update a record in any table' — this directly modifies existing data in ServiceNow tables.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

table_update Rate-limited

table_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": {
    "table_update": {
      "limits": [
        {
          "counter": "table_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about table_update

What does the table_update tool do? +

Update a record in any table. It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on table_update? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for table_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 MCP Server. Nothing to install.

What risk level is table_update? +

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

Can I rate-limit table_update? +

Yes. Add a rate_limit block to the table_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 table_update completely? +

Set action: deny in the PolicyLayer policy for table_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 table_update? +

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