Adds internal work notes (updates the 'work_notes' field) to an existing incident.
AI agents use add_work_notes_to_incident 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 modifies data (work notes field on an incident record) in a reversible manner. It does not execute code, delete data, or transfer funds. Work notes are internal annotations that can be edited or removed, making this a Write operation.
From the tool's definition Tool name 'add_work_notes_to_incident' and description 'Adds internal work notes (updates the 'work_notes' field) to an existing incident' indicates modification of an existing record's field.
Documented attack patterns abuse exactly the kind of access add_work_notes_to_incident 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 add_work_notes_to_incident:
{
"version": "1",
"default": "deny",
"tools": {
"add_work_notes_to_incident": {
"limits": [
{
"counter": "add_work_notes_to_incident_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_work_notes_to_incident 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.
Adds internal work notes (updates the 'work_notes' field) to an existing incident. 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 add_work_notes_to_incident: 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.
add_work_notes_to_incident 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_work_notes_to_incident 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_work_notes_to_incident. 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_work_notes_to_incident 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.