execute_dml_statement · Snowflake Developer MCP Server MCP

WHAT IT DOES

What execute_dml_statement does on Snowflake Developer MCP Server

AI agents invoke execute_dml_statement to trigger actions in Snowflake Developer MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_dml_statement needs a policy

This tool permits execution of arbitrary DML statements whose effects depend entirely on the AI agent's reasoning and input. While DML does not typically include Destructive operations like DROP (which are DDL), DELETE statements within DML can irreversibly remove data. However, DML primarily enables data modification (INSERT, UPDATE, MERGE) and procedure calls, placing it in Execute rather than Destructive.

From the tool's definition Tool name 'execute_dml_statement' combined with description 'Execute a custom DML statement for data operations' indicates execution of arbitrary Data Manipulation Language statements. DML covers INSERT, UPDATE, DELETE, MERGE, and CALL operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_dml_statement Rate-limited

execute_dml_statement stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_dml_statement": {
      "limits": [
        {
          "counter": "execute_dml_statement_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Snowflake Developer MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_dml_statement

What does the execute_dml_statement tool do? +

Execute a custom DML statement for data operations. It is categorised as a Execute tool in the Snowflake Developer MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_dml_statement? +

Register the Snowflake Developer MCP Server MCP server in PolicyLayer and add a rule for execute_dml_statement: 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.

What risk level is execute_dml_statement? +

execute_dml_statement is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_dml_statement? +

Yes. Add a rate_limit block to the execute_dml_statement 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.

How do I block execute_dml_statement completely? +

Set action: deny in the PolicyLayer policy for execute_dml_statement. 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.

What MCP server provides execute_dml_statement? +

execute_dml_statement 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.