How to Configure JetBrains AI Cassandra Read Only Permissions

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up jetbrains ai cassandra read only permissions by creating a restricted database role. Then you assign that role to the database tool inside your code editor. Many engineering teams start by sharing a single admin login for fast local testing. This habit puts live data at risk when an AI assistant runs queries. A bad prompt can trigger a delete or update command on important tables. Scoping the database role to read actions stops the AI from changing records. How jetbrains ai cassandr

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 cassandra read only permissions by creating a restricted database role. Then you assign that role to the database tool inside your code editor. Many engineering teams start by sharing a single admin login for fast local testing. This habit puts live data at risk when an AI assistant runs queries. A bad prompt can trigger a delete or update command on important tables. Scoping the database role to read actions stops the AI from changing records.

How jetbrains ai cassandra read only permissions work in practice

The code editor uses its built-in database tool to talk to the cluster. The AI assistant reads the database schema from this local tool to write queries. When a developer asks the assistant to run a query, it uses those stored credentials. Cassandra manages permissions through its native role-based system inside the cluster itself.

An admin creates a specific role for the editor and turns on login privileges. Instead of granting all rights, the admin grants only the select permission. You can apply this rule to the whole cluster or a single keyspace. You can also restrict the role to specific tables that hold safe data. Once the admin finishes the Cassandra role setup, the developer logs in from the editor. Every query from the AI assistant now runs under that strict select rule.

What native read roles solve and where they fall short

Native select roles stop accidental writes, drops, and schema changes right at the database. If the AI assistant suggests a drop table statement, the cluster rejects it right away. This setup protects data integrity during daily coding and debugging sessions. Still, native database roles only check who logs in at the start of a session. They cannot inspect what individual statements do while they run in flight.

A read-only role still lets the editor pull sensitive customer records from allowed tables. When the AI assistant reads query results, raw data goes into the model prompt. Native permissions cannot mask emails, phone numbers, card numbers, or national IDs in results. Data masking is needed to rewrite matched fields in results before the editor sees them. Also, a read-only role does not stop heavy queries that scan a whole cluster. A bad select statement without a partition key can still slow down production nodes.

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

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Why static credentials in the code editor create audit gaps

Storing long-lived passwords on developer laptops creates another big security gap for teams. If five developers share one read-only role, the database logs show one username. Security teams cannot tell which person or AI prompt ran a specific select query. Rotating that shared password breaks the workflow for every developer on the team at once. Teams need user-level visibility and field-level controls that static database roles cannot provide.

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 JetBrains AI change data if the Cassandra role only has select rights?

No, the database cluster blocks any write, update, or delete commands from that role. The editor will receive a permission error if the AI tries to change data.

Does a read-only role stop the AI assistant from sending sensitive data to the model?

No, a read-only role still returns full rows from every allowed table. Without dynamic data masking, raw emails or card numbers can enter the AI context.

How do we restrict the AI assistant to specific Cassandra tables?

Your database admin must grant the select permission only on individual tables or keyspaces. Avoid granting select rights at the root resource level of the cluster.

The query runs. The emails stay hidden.