submit_change_for_approval · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What submit_change_for_approval does on ServiceNow-MCP

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

WHY IT NEEDS A POLICY

Why submit_change_for_approval needs a policy

This tool modifies data (advances a change request through workflow) but does not delete, destroy, or execute arbitrary operations. The action is reversible (a change can be un-submitted or returned to prior states in typical ServiceNow workflows).

From the tool's definition Tool name 'submit_change_for_approval' indicates modification of change request state. Description is incomplete ('Move a change request to') but clearly describes state transition—a reversible write operation on a ServiceNow change management object.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_change_for_approval Rate-limited

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

FAQ

Questions about submit_change_for_approval

What does the submit_change_for_approval tool do? +

Move a change request to. It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_change_for_approval? +

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

What risk level is submit_change_for_approval? +

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

Can I rate-limit submit_change_for_approval? +

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

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

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