SaturnSQL GuardComing soon

Decide what AI agents can do in your databases

Your team wants Claude, ChatGPT and Cursor on company data. Say yes and keep the final say: each person’s AI sees only what they may see, changes wait for a person, and every question has a name on it.

See plans

€29/user/month · Pro plan

AI tool access
ConnectionAccess
prod-postgres
PostgreSQL · app
Read-only
finance
PostgreSQL · reports
Shared queries only
billing
SQL Server · billing
Off
staging
PostgreSQL · staging
Same as the user
Approve request
WaitingChange dataonstaging
Person
Dana
From
AI tool · Claude
UPDATE orders SET status = 'refunded' WHERE id = 4182;
ApproveDecline

Your team wants AI on company data. Security wants control.

Give both of them what they need.

Who asked the AI for that?

With SaturnSQL, every AI question has a name on it.

The AI asked for customer emails. It didn’t get them.

Keep personal data out of AI answers, every time.

Sales shouldn’t see salaries. Neither should their AI.

Everyone, and every AI they use, sees only the data that’s theirs.

You can’t predict what AI will ask your database

Decide which questions it may answer, and nothing more.

People leave. Their AI access shouldn’t stay.

SaturnSQL makes sure it doesn’t.

The auditor wants every AI query. Can you show them?

Be ready with the full record instead of a scramble.

Not just on or off

Trust AI as far as each database deserves, and change your mind any time.

Off

AI can’t see the database at all. People keep using it as usual.

Shared queries only

AI can only ask the questions your team has already saved and shared.

Read-only

AI can look, but can’t change anything, even where its person could.

Same as the user

AI can do what its person can. Changes wait for a yes by default.

Risky queries wait for a person

Before an AI changes or exports data, the right person hears about it in Slack or by email, sees exactly what it wants to run, and says yes once or for the afternoon.

Claude · execute_write_queryAPPROVAL_REQUIRED
Approval needed. Ask the user to approve it at saturnsql.com/app/approve/cm9x…, then repeat this request with approvalId.
Approve request
WaitingChange dataonstaging
Person
Dana
From
AI tool · Claude
UPDATE orders SET status = 'refunded' WHERE id = 4182;
ApproveDecline

When an agent goes too far

  1. 1

    Claude asks for customer emails. That column is hidden from Dana’s group, so the query is blocked before it reaches the database.

  2. 2

    Claude wants to delete old orders on staging. Guard holds it, Dana reads the SQL and approves, and it runs once.

  3. 3

    Cursor reaches for billing, which is off for AI tools. Blocked, with the reason, under Sam’s name.

Audit log
10:46SamAI tool · CursorBlocked–
SELECT * FROM invoices
Access through AI tools is off for this connection.
10:45DanaAI tool · ClaudeRan1,204
DELETE FROM orders WHERE created_at < '2025-01-01';
10:44DanaAI tool · ClaudeBlocked–
SELECT name, email FROM customers
customers.email is hidden from you.
10:42DanaAI tool · ClaudeRan3
SELECT region, sum(total) FROM orders GROUP BY 1

Also in Guard

Each team sees only its own data

Sales sees its own customers, the EU team sees EU rows, contractors see only the tables they need, and personal data can be hidden or masked. Their AI tools follow the same rules.

No runaway AI queries

Keep every AI question small enough to be safe for your app, and cheap enough for your BigQuery bill, for each database or team.

Answer the auditor in minutes

Every query is on record, from people and from AI, including the ones that were blocked and why.

Every AI question has a name on it

Each person connects their AI tool with their own account, so you always know who asked. No shared keys, no anonymous service accounts.

AI tools never hold your passwords

Database credentials stay encrypted on SaturnSQL’s servers and never reach the AI tool or anyone’s laptop.

The full detail is in database governance for MCP and AI, on the security page, and in how to set access rules for a group. On the same plan, SaturnSQL Context helps AI tools understand the data they may see.

AI governance checklist

ControlHow SaturnSQL does it
Choose which databases AI can reachAI tool access set per connection: Off, Shared queries only, Read-only or Same as the user (Guard)
Only the team's questionsShared queries only: AI tools run the team's shared saved queries and fill in their variables, never their own SQL (Guard)
AI cannot change dataRead-only accepts one SELECT, WITH or EXPLAIN per call
A person approves risky requestsChanges, exports or every request wait until the user or an admin approves them, once or for 1 to 8 hours, alerted in Slack or by email (Guard)
Cap what AI queries return and costRows per query, queries a minute per person, timeout and BigQuery bytes billed, set for each database or group (Guard)
Limit tables, columns and rowsAccess rules per group, with hidden or masked columns, checked by SaturnSQL (Guard), backed by a restricted database user
Credentials never reach the modelEncrypted with AES-256, kept server-side
Every AI query tied to a personOAuth sign-in per person, no shared key
Full record per connectionAudit log with person, client, full SQL and rows, exportable as CSV (Guard)
Only owners change the rulesAI tool access is editable by the connection owner and admins
No database open to the internetStatic egress IP, SSH bastion, TLS with your own CA

Questions about Guard

What is SaturnSQL Guard?
Guard is SaturnSQL’s AI access control for teams that let AI tools such as Claude, ChatGPT and Cursor query company databases over MCP. It sets what AI tools can do on each database connection, holds risky requests until a person approves them, limits tables, columns and rows per person, and records every query in an audit log. It comes with the Pro plan, €29 per user per month with everything in Starter.
How do I stop Claude from writing to my production database?
Set the connection’s AI tool access to Read-only, which is the default. Claude, ChatGPT, Cursor and API keys can then run one SELECT, WITH or EXPLAIN per call, even when the person could write in the editor. To let an AI tool make changes on a database like staging, choose Same as the user, and each change waits for the user or an admin to approve it.
Can I restrict which tables an AI agent can see?
Yes. Access rules give each person only some tables, or all tables except some, and can hide or mask columns and filter rows. The rules follow the person into the editor and into every AI tool they connect, and hidden tables and columns are left out of the schema the AI tool sees. To hide a whole database from AI tools, set its AI tool access to Off.
How does an approver know a request is waiting?
SaturnSQL sends whoever can approve it, the user or the admins, a Slack message with the SQL and a link, or an email when Slack can’t reach them. They can approve it once, or for 1, 4 or 8 hours so the same kind of request from that person runs without asking again. The person whose AI tool asked is told when it is approved.
Can an AI tool approve its own request or change the rules?
It can never approve its own request. It can change Guard settings only after an admin approves that for that one AI tool or API key in SaturnSQL, and only for 12 hours at a time, after which it has to ask again. Every change is recorded with the person’s name, and the audit log can only be read in SaturnSQL.
Which databases does Guard work with?
AI tool access, approvals and the audit log work on every database SaturnSQL connects to. Access rules work on PostgreSQL, Redshift, MySQL, SQL Server and BigQuery.
What does Guard not do?
Access rules are a guard, not the lock: SaturnSQL checks the SQL before it runs but cannot see inside database functions or views, so pair the rules with a restricted database user, whose setup SQL Guard can write for PostgreSQL and MySQL. Masked columns are masked by SaturnSQL, so the restricted database user still reads them in full. Guard only sees queries that go through SaturnSQL, so an AI tool given its own database password is outside it.
How much does Guard cost?
Guard comes with the Pro plan: €29 per user per month, billed monthly, with everything in Starter. Pro is coming soon. Join the waitlist to hear when it opens.

Comparing tools? See the best MCP gateways for databases or StrongDM alternatives.

SaturnSQL GuardComing soon

Make your AI rollout easy to approve

Give security the control it asks for, from day one.

See plans

€29/user/month

Pro plan: everything in Starter, plus

  • Context: notes for AI, definitions, and table and column descriptions every AI tool reads with the schema
  • AI tool access per connection: off, shared queries only, read-only or same as the user
  • Approvals: risky AI tool requests wait for a person, alerted in Slack or by email
  • Limits on AI tool queries for each database or group: rows per query, queries a minute per person, timeout, BigQuery bytes
  • Access rules per group: hide tables, hide or mask columns, filter rows
  • Audit log of every query, from people and AI
  • Query version history

Use Cases

Collaborative SQL Editor for TeamsAd-Hoc Analysis for AnalystsOps & Debugging for EngineersAI-Assisted SQL EditorReverse ETLSelf-Service AnalyticsPopSQL AlternativesSeekWell Alternatives

Help

Getting StartedConnecting a DatabaseRunning QueriesMigrate from PopSQLMigrate from SeekWellAPI ReferenceContact SupportReviews on G2

Learn SQL

PostgreSQL GuidesMySQL GuidesSQL Server GuidesOracle GuidesBigQuery GuidesSnowflake GuidesRedshift GuidesClickHouse Guidesdbt GuidesAll SQL GuidesCron Expression Generator

Compare

SaturnSQL vs HexSaturnSQL vs DBeaverSaturnSQL vs MetabaseSaturnSQL vs ModeBlogChangelog

Company

Privacy PolicyTerms & ConditionsAcceptable Use PolicyData Processing AgreementDesktop AppSaturnSQL ContextSaturnSQL GuardEnterpriseAboutGDPR Compliant
SaturnSQL - Featured on Startup Fame

© 2026 Panda Capital Oy Ab. All rights reserved.