Attaches a file to any record in ServiceNow. The file content must be Base64 encoded.
AI agents use attach_file_to_record 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.
This tool creates or adds file attachments to ServiceNow records, which is a write operation (data modification). It is reversible since attachments can be deleted. The severity is medium because an agent could attach malicious files to records (potentially affecting organizational security or records integrity), but the operation itself is not destructive or financial.
From the tool's definition Tool description: 'Attaches a file to any record in ServiceNow.' The verb 'attaches' indicates creation/addition of data to existing records, a reversible modification operation.
Documented attack patterns abuse exactly the kind of access attach_file_to_record gives an agent:
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 attach_file_to_record:
{
"version": "1",
"default": "deny",
"tools": {
"attach_file_to_record": {
"limits": [
{
"counter": "attach_file_to_record_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}attach_file_to_record 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.
Free to start. No card required.
Attaches a file to any record in ServiceNow. The file content must be Base64 encoded. 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.
Register the Snow MCP server in PolicyLayer and add a rule for attach_file_to_record: 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.
attach_file_to_record 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 attach_file_to_record 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 attach_file_to_record. 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.
attach_file_to_record 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.
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.