Update existing data in a Snowflake table
AI agents use update_data to create or update resources in Snowflake Developer MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Snowflake Developer MCP Server environment.
This tool creates or modifies data reversibly. Updates to table data can be rolled back or corrected, distinguishing it from destructive operations (delete_data, drop_database_object). While it modifies data and could impact business logic if misused, it does not irreversibly destroy information or execute arbitrary code.
From the tool's definition Tool name 'update_data' and description 'Update existing data in a Snowflake table' indicate modification of existing data in a reversible manner.
Attacks that exploit this kind of access
Update existing data in a Snowflake table. It is categorised as a Write tool in the Snowflake Developer MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Snowflake Developer MCP Server MCP server in PolicyLayer and add a rule for update_data: 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 Snowflake Developer MCP Server. Nothing to install.
update_data 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 update_data 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 update_data. 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.
update_data is provided by the Snowflake Developer MCP Server MCP server (mcp-tg/snowflake-developer-kit). 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 →