What you can ask
“What databases and tables do we have in Snowflake?”
“How many orders did we book last quarter, by region?”
“Which market segment has the most customers? Exact numbers, please.”
“How many Snowflake credits did we burn this week, per warehouse?”
“What were our most expensive queries in the last 30 days?”
Connecting
Setup takes a few minutes and one copy-paste — no passwords and no key files.- Open Connections in the dashboard, click Snowflake → Connect, and
paste the web address from your browser while you’re logged into
Snowflake (an account identifier like
MYORG-MYACCOUNTworks too). Add the warehouse the agent may use. - Click Generate setup script. Expertise creates a key pair on the spot — the private key goes straight into our secret store and is never shown to anyone — and gives you a short SQL script with the public key already embedded.
- Run the script in a Snowflake worksheet (the dialog has an Open Snowflake worksheets button). It is a single statement, so any Run button runs all of it, and it works unchanged for regular databases and shares. It creates a read-only role and a key-based service user — nothing else in your account is touched. Not the Snowflake admin? Send the script to whoever is; that’s the only step that needs one.
- Back in the dialog, click Test connection. You’ll see how many databases the agent can now read.
DROP USER <the service user from your script>;.
Tools
Every tool is read-only — there are no write tools, by design.Good to know
- The agent can never write. Three independent layers enforce it: the role your script creates holds SELECT-only grants (Snowflake itself refuses writes), Expertise rejects any non-read statement before it is sent, and there simply are no write tools.
- Runaway queries can’t run up your bill. Every query carries a statement timeout (up to 5 minutes), results are row- and size-capped, and metadata reads (listing, describing) use no warehouse compute at all.
- Cost tracking is opt-in.
snowflake_usage_and_costsneeds the optionalGRANT IMPORTED PRIVILEGES ON DATABASE SNOWFLAKEline that ships commented in your setup script — uncomment it to enable spend reporting. - Cortex features follow your account. AI functions, Cortex Search, and Cortex Analyst work where your Snowflake account has Cortex enabled and the services/semantic models exist; otherwise the agent reports Snowflake’s own message rather than guessing.
- You control exposure with grants. The agent sees exactly what the read-only role is granted — extend or narrow access any time in Snowflake.
Troubleshooting
Test connection says the key was rejected
Test connection says the key was rejected
The setup script didn’t finish in Snowflake — its final
ALTER USER
line is what registers the key. Re-run the whole script (it’s safe to
run repeatedly) and test again. If you regenerated the script after a
disconnect, only the newest script’s key is valid.Warehouse errors when running queries
Warehouse errors when running queries
The error lists the warehouses the agent can use. If the list is
empty, the script’s
GRANT USAGE ON WAREHOUSE line didn’t run or names
a warehouse that doesn’t exist — fix the name from Back to account
details and re-run the script.