publish_changeset

THE RISK

High Risk

Why publish_changeset needs a policy

Publishing a changeset triggers an external operation that deploys code/configuration changes to a remote ServiceNow instance. This is an execution-class action with significant blast radius — pushing bad code or configurations to production could break services.

From the tool's definition 'Publish a completed changeset so it can be retrieved from the remote instance'

Documented attack patterns abuse exactly the kind of access publish_changeset gives an agent:

POLICY

How to control publish_changeset

PolicyLayer is an MCP gateway — it sits between your AI agents and Snow, and nothing reaches the server without passing your rules. This is the rule we recommend for publish_changeset:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "publish_changeset": {
      "limits": [
        {
          "counter": "publish_changeset_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register Snow — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Snow tools

Destructive delete_script_include Delete a Script Include from ServiceNow. Destructive delete_story_dependency Deletes an existing dependency relationship between user stories. Destructive delete_workflow Delete a workflow definition from ServiceNow. Destructive remove_group_members Remove multiple users from a group. Write add_change_task Adds a new task to an existing change request. Write add_comment_to_incident Adds a customer-visible comment (updates the 'comments' field) to an existing incident. Write add_comment_to_request Adds a customer-visible comment to a request ticket (REQ). Write add_file_to_changeset Add (track) a configuration record inside the specified changeset.

All 88 Snow tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Snow → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about publish_changeset

What does the publish_changeset tool do? +

Publish a completed changeset so it can be retrieved from the remote instance. It is categorised as a Execute tool in the Snow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on publish_changeset? +

Register the Snow 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 Snow. Nothing to install.

What risk level is publish_changeset? +

publish_changeset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit publish_changeset? +

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.

How do I block publish_changeset completely? +

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.

What MCP server provides publish_changeset? +

publish_changeset is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Snow tool call.

Start from Snow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →