execute_sql_query · Snowflake Developer MCP Server MCP

WHAT IT DOES

What execute_sql_query does on Snowflake Developer MCP Server

AI agents invoke execute_sql_query 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_sql_query needs a policy

While execute_sql_query itself is categorized as Execute (running arbitrary code/queries with effects dependent on user input), it is severely elevated to critical severity because: (1) it operates on a production database system (Snowflake), (2) custom SQL queries can include DELETE, DROP, or other destructive operations that would technically be Destructive but are enabled through this Execute tool, (3) an AI…

From the tool's definition Tool name: 'execute_sql_query'; description: 'Execute a custom SQL query on Snowflake'. The sibling tools include destructive operations (drop_database_object, delete_data) and write operations (create_table, alter_table), indicating this server manages…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_sql_query Rate-limited

execute_sql_query 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_sql_query": {
      "limits": [
        {
          "counter": "execute_sql_query_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_sql_query

What does the execute_sql_query tool do? +

Execute a custom SQL query on Snowflake. 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_sql_query? +

Register the Snowflake Developer MCP Server MCP server in PolicyLayer and add a rule for execute_sql_query: 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_sql_query? +

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

Can I rate-limit execute_sql_query? +

Yes. Add a rate_limit block to the execute_sql_query 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_sql_query completely? +

Set action: deny in the PolicyLayer policy for execute_sql_query. 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_sql_query? +

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