Add a file to a changeset
AI agents use add_file_to_changeset 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.
This tool creates or modifies changeset contents by adding files, which is a reversible operation (files can be removed). While it affects change management workflows and could impact deployed systems if the changeset is later committed, the add operation itself is not destructive—no data is permanently deleted or overwritten. It falls under Write category.
From the tool's definition Tool name 'add_file_to_changeset' and description 'Add a file to a changeset' indicate a file addition/modification operation within a ServiceNow changeset management workflow.
Attacks that exploit this kind of access
Add a file to a changeset. 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 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 ServiceNow MCP Server. Nothing to install.
add_file_to_changeset 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 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.
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.
add_file_to_changeset is provided by the ServiceNow MCP Server MCP server (shameerampcome/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 →