Summary
One tool means the model writes the SQL, and the grants on the connection are the only boundary.
execute_query takes a query and nothing else — no schema listing, no row cap, no separate read-only path — so whatever the Snowflake connection is allowed to do is what a client can do through it. That puts the interesting decision before installation rather than after it: the account and role you point it at define the blast radius. In return there is nothing to learn, since anything expressible in SQL is already in scope.
What it is
A single-tool bridge to a Snowflake database: one SQL query in, its result out.
What you get
- execute_query runs a SQL query on the Snowflake database over the connection the server holds and returns the result of the execution.
Requirements
A Snowflake database and a connection for the server to run queries over.
Setup effort
One command plus a key — uvx snowflake-mcp, then supply credentials