publish_changeset
Publish/export an update set to XML for deployment (requires SCRIPTING_ENABLED=true)
This record as markdown: /tools/servicenow-mcp-server/publish-changeset.md
What publish_changeset does on ServiceNow MCP Server
AI agents invoke publish_changeset to trigger actions in ServiceNow MCP Server. 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.
Why publish_changeset is rated High
Publishing/exporting an update set for deployment triggers an external operation that pushes configuration changes into a ServiceNow environment. The 'SCRIPTING_ENABLED=true' requirement indicates this can execute scripts as part of the deployment process.
From the tool's definition Publish/export an update set to XML for deployment (requires SCRIPTING_ENABLED=true)
Attacks that exploit this kind of access
The rule that runs publish_changeset 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 publish_changeset, this is the rule to start with:
publish_changeset stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 publish_changeset call is checked against it from then on.
Questions about publish_changeset
Publish/export an update set to XML for deployment (requires SCRIPTING_ENABLED=true). It is categorised as a Execute tool in the ServiceNow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ServiceNow MCP Server 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 Server. 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 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.
Across the catalogue