submit_change_for_approval
Move a change request to
This record as markdown: /tools/servicenow-mcp-server/submit-change-for-approval.md
What submit_change_for_approval does on ServiceNow MCP Server
AI agents use submit_change_for_approval 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 submit_change_for_approval is rated Medium
The tool appears to transition a change request record to an approval state in ServiceNow. This is a state/status modification of an existing record — reversible by moving it back — placing it in the Write category. Severity is medium because submitting a change for approval can trigger workflows and notifications, but it does not directly execute, delete, or commit financial transactions.
From the tool's definition 'submit_change_for_approval' and 'Move a change request to' (description is truncated/incomplete)
Attacks that exploit this kind of access
The rule that runs submit_change_for_approval safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For submit_change_for_approval, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every submit_change_for_approval call is checked against it from then on.
Questions about submit_change_for_approval
Move a change request to. 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.
Register the ServiceNow MCP Server 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 Server. Nothing to install.
submit_change_for_approval 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 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.
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.
submit_change_for_approval is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue