Submits a change request for approval by setting its state to 'Assess'.
AI agents use submit_change_for_approval 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 (updates a change request's state) without permanently deleting or destroying records. The operation is reversible — the change state can be reset to a previous value if needed. While it has organizational impact (triggering approval workflows), it does not execute arbitrary code, delete data, or move financial resources.
From the tool's definition Submits a change request for approval by setting its state to 'Assess' — this modifies the state field of an existing change record, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access submit_change_for_approval 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 submit_change_for_approval:
{
"version": "1",
"default": "deny",
"tools": {
"submit_change_for_approval": {
"limits": [
{
"counter": "submit_change_for_approval_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}submit_change_for_approval 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.
Submits a change request for approval by setting its state to 'Assess'. 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 submit_change_for_approval: 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.
submit_change_for_approval 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 submit_change_for_approval 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 submit_change_for_approval. 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.
submit_change_for_approval 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.