reject_change · ServiceNow MCP Server MCP: Risk & Policy

WHAT IT DOES

What reject_change does on ServiceNow MCP Server

AI agents use reject_change 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 reject_change needs a policy

This operation modifies data (the change request record's status) but does not irreversibly delete it or execute arbitrary code. The rejection can be undone by resubmitting or changing the record state again. It falls under Write rather than Execute because it performs a specific state transition rather than arbitrary command execution.

From the tool's definition Tool name is 'reject_change' and description states 'Reject a change request'. This modifies the status/state of an existing change record in ServiceNow by transitioning it from pending approval to rejected, which is a reversible state change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reject_change Rate-limited

reject_change 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": {
    "reject_change": {
      "limits": [
        {
          "counter": "reject_change_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 reject_change

What does the reject_change tool do? +

Reject a change request. 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 reject_change? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for reject_change: 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 reject_change? +

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

Can I rate-limit reject_change? +

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

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

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