How to Configure JetBrains AI Snowflake Read Only Permissions

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up jetbrains ai snowflake read only permissions by creating a custom role. You grant select rights to that role and assign it to the user. Many engineering teams skip this step and use shared admin accounts in their code editors. Broad database permissions let an AI assistant change or delete production tables by mistake. A strict read role stops the tool from running write commands on your data warehouse. How to set up jetbrains ai snowflake read only permissions Snowflake uses role-

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.

You set up jetbrains ai snowflake read only permissions by creating a custom role. You grant select rights to that role and assign it to the user. Many engineering teams skip this step and use shared admin accounts in their code editors. Broad database permissions let an AI assistant change or delete production tables by mistake. A strict read role stops the tool from running write commands on your data warehouse.

How to set up jetbrains ai snowflake read only permissions

Snowflake uses role-based permissions to manage what users and tools can do. You start by making a new role just for your development tools. Next, you grant usage rights on the warehouse, database, and schema to this role. Then you grant select permissions on the specific tables the team needs to read. You also apply this rule to future tables so the setup stays current.

After the role is ready, you assign it to a dedicated user account. You then set this read role as the default role for that user. Inside the JetBrains editor, the developer opens the database tool window. They enter the user credentials and specify the read-only role in the session settings. JetBrains AI uses the schema details from this database session to write queries.

When the developer asks the AI to build a query, it reads the table structure. If the developer runs the generated SQL, the warehouse checks the active role first. If the query tries to drop a table or update rows, the warehouse blocks it. This native setup keeps your core data safe from accidental writes or deletes.

What native roles solve and what they miss

Native database roles are great at stopping write commands at the warehouse level. They ensure that an AI tool or developer cannot alter table structures or delete rows. They also let you split warehouse compute costs by giving the AI role a small warehouse. This stops heavy test queries from slowing down your main production reports.

Still, static roles only decide who can log in and which tables they can read. They do not inspect what individual queries do in flight during an active session. Once a user has select rights on a table, they can read every column inside it by default. The AI assistant can pull raw customer emails, phone numbers, or card numbers into prompts. Static roles cannot rewrite sensitive fields in query results without extra masking rules on every column by default.

AI Agent Permissions + Read-Only Root Filesystem: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Why local editor keys create security gaps

Setting up a read-only role still requires giving a password or key to each developer. Those static credentials sit on local laptops inside the code editor storage. If a laptop is lost or malware hits the machine, the attacker gets those keys. Rotating these keys across a large engineering team takes hours of manual work.

Shared roles also make auditing very hard for security teams. When five developers use the same service account, the query log shows one user name. You cannot tell which person ran a heavy query or pulled sensitive customer rows. You also cannot require a quick human check before someone runs a massive select statement.

Add runtime guardrails and masking beside your databases and APIs

Login rules, role grants, and CI checks govern who connects to your stack. Yet any allowed script, engineer, or AI agent still runs commands with the full scope of its role. For workloads on Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes, SSH, or internal HTTP services, hoop.dev sits beside the service as an open-source proxy, a sidecar for your database or API.

Before a query runs, hoop.dev guardrails check the statement against your rules. An AI Analyzer you configure can score intent or hold risky calls for human review. Next, hoop.dev data masking rewrites sensitive fields in responses, and each verdict is logged per listener. Explore the MIT-licensed project on GitHub.

Frequently asked questions

Can JetBrains AI change data if the user has a secondary admin role?

Yes, if the database session allows role switching, the user or tool can activate the higher role. You must restrict the session to the read role and disable automatic secondary roles for that user.

Does a read-only role hide sensitive columns from AI prompts?

No, a standard select grant lets the user read all columns in a table by default. Unless you set up dynamic data masking to rewrite emails or phone numbers, those fields appear in results.

How do we stop AI-generated queries from running up warehouse costs?

Assign the read-only role to a small dedicated warehouse with a strict timeout limit. This stops bad joins or full table scans from burning through your compute credits.

The query runs. The emails stay hidden.