query_snowflake · Snowflake MCP Server MCP: Risk & Policy

WHAT IT DOES

What query_snowflake does on Snowflake MCP Server

AI agents invoke query_snowflake to trigger actions in Snowflake 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 query_snowflake needs a policy

Executing arbitrary SQL can include DML (INSERT, UPDATE, DELETE), DDL (DROP, ALTER, TRUNCATE), or data exfiltration queries. While the server description emphasizes read-oriented workflows, the tool itself places no stated restriction on query type. A misconfigured or malicious prompt could cause irreversible data loss or unauthorized data access.

From the tool's definition "Execute a SQL query on Snowflake and return results" — the tool runs arbitrary SQL against a Snowflake data warehouse.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query_snowflake Rate-limited

query_snowflake 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": {
    "query_snowflake": {
      "limits": [
        {
          "counter": "query_snowflake_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about query_snowflake

What does the query_snowflake tool do? +

Execute a SQL query on Snowflake and return results. It is categorised as a Execute tool in the Snowflake 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 query_snowflake? +

Register the Snowflake MCP Server MCP server in PolicyLayer and add a rule for query_snowflake: 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 MCP Server. Nothing to install.

What risk level is query_snowflake? +

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

Can I rate-limit query_snowflake? +

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

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

query_snowflake is provided by the Snowflake MCP Server MCP server (legolasan/snowflake_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

query_snowflake is one line of Snowflake MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →