Execute a SQL query on Snowflake and return the result as JSON
AI agents invoke execute-snowflake-sql to trigger actions in Simple Snowflake MCP. 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.
This tool can run any SQL statement a user composes, including SELECT (Read), INSERT/UPDATE (Write), DELETE (Destructive), or DDL operations. Without restrictions on query content shown in the description, it is classified as Execute because the actual impact depends entirely on the SQL provided as an argument.
From the tool's definition Tool description states 'Execute a SQL query on Snowflake' — the verb 'Execute' indicates running arbitrary SQL commands.
Documented attack patterns abuse exactly the kind of access execute-snowflake-sql gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Simple Snowflake MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for execute-snowflake-sql:
{
"version": "1",
"default": "deny",
"tools": {
"execute-snowflake-sql": {
"limits": [
{
"counter": "execute-snowflake-sql_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute-snowflake-sql 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.
Free to start. No card required.
Execute a SQL query on Snowflake and return the result as JSON. It is categorised as a Execute tool in the Simple Snowflake MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Simple Snowflake MCP server in PolicyLayer and add a rule for execute-snowflake-sql: 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 Simple Snowflake MCP. Nothing to install.
execute-snowflake-sql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute-snowflake-sql 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 execute-snowflake-sql. 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.
execute-snowflake-sql is provided by the Simple Snowflake MCP server (yannbrrd/simple_snowflake_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Simple Snowflake MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Simple Snowflake MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.