Delete data from a Snowflake table with safety checks
AI agents call delete_data to permanently remove resources in Snowflake Developer MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting data from production tables is irreversible and has severe blast radius if misused by an AI agent (e.g., deleting entire customer records, financial transactions, or audit logs). Even with 'safety checks' mentioned, the core function is permanent data removal.
From the tool's definition Tool name is 'delete_data' and description states it 'Delete[s] data from a Snowflake table'. This is an irreversible data deletion operation. Sibling tools include 'drop_database_object' which confirms this server handles destructive operations.
Attacks that exploit this kind of access
Delete data from a Snowflake table with safety checks. It is categorised as a Destructive tool in the Snowflake Developer MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Snowflake Developer MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_data is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →