How to Configure Continue Snowflake Read Only Permissions
To set up continue snowflake read only permissions, create a read role in your warehouse. Then bind that role to the account your AI tool uses to log in. Engineering teams often reuse broad developer credentials when they set up local coding assistants. Broad permissions let an AI tool alter tables or delete production rows by mistake. A strict read role stops the assistant from writing data during a session. How continue snowflake read only permissions work in practice Setting up this workfl
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
To set up continue snowflake read only permissions, create a read role in your warehouse. Then bind that role to the account your AI tool uses to log in. Engineering teams often reuse broad developer credentials when they set up local coding assistants. Broad permissions let an AI tool alter tables or delete production rows by mistake. A strict read role stops the assistant from writing data during a session.
How continue snowflake read only permissions work in practice
Setting up this workflow starts inside your cloud data warehouse. An admin creates a dedicated role that only holds privileges to read data. First, the role needs usage rights on the compute warehouse to run queries. Next, the admin grants usage rights on the specific database and schema. Finally, the admin grants select privileges on the tables and views needed for context.
Future tables in that schema also need a default select grant. Without future grants, the coding assistant loses visibility when teams add new tables. After building the role, the admin creates a dedicated service user for the tool. The admin assigns the read role as the default role for that user.
On the local machine, the developer configures the IDE extension to use those credentials. The extension reads schema metadata and sample rows through a local context provider. Because the warehouse enforces role permissions, any write query from the assistant fails right away. The database blocks drop, delete, update, and insert statements before they touch any table.
Where native warehouse roles fall short for AI tools
Native warehouse roles solve the first major risk of AI coding tools. They stop accidental writes, schema drops, and bad data edits from happening. Still, database roles only decide who can log in and which tables they can read. They do not inspect what individual select statements do while they run.
A read role still allows the assistant to pull every column in an allowed table by default. Customer tables often hold emails, phone numbers, card numbers, and national IDs. When the assistant runs a sample query, those sensitive fields enter the IDE prompt. From there, the raw values travel to the external model provider.
Read-Only Root Filesystem + Snowflake Access Control: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Native roles also struggle with shared static keys stored on developer laptops. Developers must store a password or private key in a local text file. If a laptop gets lost, an attacker can use that key to read data. Revoking or rotating those local keys across a large team takes hours of manual work.
How to protect sensitive data during AI queries
Teams need controls that work at the query level, not just the role level. Before a coding tool reads a table, you should limit how many rows return. You can create filtered views that only expose safe columns for AI context. Views let you leave out columns with emails, phone numbers, or card numbers.
You should also set strict resource timeouts on the compute warehouse used by the assistant. An AI tool might write a bad join that scans billions of rows. A short query timeout stops runaway read queries from burning through compute credits. Combining small warehouses, short timeouts, and restricted views keeps your data and budget safe.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.
First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
Can a read role still run up high warehouse compute bills?
Yes, a read role can still run heavy select queries that scan huge tables. Set a short statement timeout and use your smallest compute warehouse to cap costs.
How do we stop the AI assistant from reading sensitive customer columns?
Do not grant select rights on raw customer tables with emails or card numbers. Grant read permissions on secure views that leave out sensitive fields or mask values.
Should every developer share one database user for their AI coding tool?
No, sharing one user hides which developer ran a specific query in the logs. Give each developer a separate user tied to the same read role for clear tracking.
Related guides
In this post