Publish/export an update set to XML for deployment (requires SCRIPTING_ENABLED=true)
AI agents invoke publish_changeset to trigger actions in ServiceNow-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Publishing/exporting a changeset triggers a deployment pipeline operation in ServiceNow, executing an export process that moves configuration changes toward production. The requirement for SCRIPTING_ENABLED=true indicates it involves scripting execution.
From the tool's definition 'Publish/export an update set to XML for deployment' and 'requires SCRIPTING_ENABLED=true'
Attacks that exploit this kind of access
Publish/export an update set to XML for deployment (requires SCRIPTING_ENABLED=true). It is categorised as a Execute tool in the ServiceNow-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for publish_changeset: 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.
publish_changeset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the publish_changeset 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 publish_changeset. 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.
publish_changeset 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →