Medium Risk

add_file_to_changeset

Add (track) a configuration record inside the specified changeset.

How to control add_file_to_changeset ↓

What add_file_to_changeset does on Snow

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

Medium Risk

Why add_file_to_changeset needs a policy

This tool creates or updates data (adds a file/configuration record to a changeset) without irreversibly deleting data or executing arbitrary code. It falls into the Write category as a create/modify operation.

From the tool's definition The tool 'add_file_to_changeset' performs an 'Add' operation that creates or modifies a relationship between a configuration record and a changeset in ServiceNow's change management system.

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

How to control add_file_to_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 add_file_to_changeset:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_file_to_changeset": {
      "limits": [
        {
          "counter": "add_file_to_changeset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

add_file_to_changeset 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.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about add_file_to_changeset

What does the add_file_to_changeset tool do? +

Add (track) a configuration record inside the specified changeset. It is categorised as a Write tool in the Snow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_file_to_changeset? +

Register the Snow MCP server in PolicyLayer and add a rule for add_file_to_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 add_file_to_changeset? +

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

Can I rate-limit add_file_to_changeset? +

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

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

add_file_to_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.

Free to start. No card required.

88 Snow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.