How to Configure Goose Supabase Credentials

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up goose supabase credentials by creating a dedicated database role for your tool. Then you store that role's login details in your local tool settings. Many teams skip this step and use the default admin password to move fast. Broad roles let an autonomous agent change schemas or delete rows by mistake. How goose supabase credentials work in practice Every new project comes with a default postgres role that holds admin privileges. The platform does not grant full superuser status bec

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 goose supabase credentials by creating a dedicated database role for your tool. Then you store that role's login details in your local tool settings. Many teams skip this step and use the default admin password to move fast. Broad roles let an autonomous agent change schemas or delete rows by mistake.

How goose supabase credentials work in practice

Every new project comes with a default postgres role that holds admin privileges. The platform does not grant full superuser status because that allows destructive database tasks. Instead, the default role gets extra privileges for select admin jobs. The password you pick at project creation belongs to this default admin role. Queries you run in the web dashboard also execute under this default role. Official docs state you should never hand this password to an external service. Instead, you should make a fresh user for each tool you run.

To set up goose supabase credentials, start by making a new database user. Give this user a strong password and grant only the table rights it needs. If the agent only answers data questions, give it read rights on chosen tables. Next, copy the project host details and the new role login string. Put those values into the local environment where the agent runs its database tasks. When the agent starts a task, it reads those local values to log in. Postgres checks the user password and sets the active role for that session.

What native roles solve and what they leave open

Dedicated database roles give your team a strong first line of defense. They stop an agent from touching schemas or tables outside its assigned scope. Each tool gets its own login, so you can rotate one password alone. If you stop using a tool, you can drop its role right away. Native roles also let you separate read tasks from write tasks across projects. This setup is much safer than sharing the default admin login across laptops.

Still, native database logins only check who logs in at the start. Once the session starts, the database trusts every query that role can run. A role with read access to user tables returns every column in full by default. Query results can include raw emails, phone numbers, card numbers, or national IDs. Those values flow straight back into the agent context and model history. Also, a role that needs write access for one job can run broad deletes. Static credentials sit on local disks where scripts or other local tools can read them. Native roles cannot pause a risky command to ask a human for approval first. They also cannot rewrite sensitive fields in query results before the agent reads them.

Ephemeral Credentials + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Managing agent sessions and sensitive data

Teams running autonomous agents need controls that work on each query in flight. First, move away from storing static database passwords on developer laptops. When engineers do not hold raw passwords, credentials cannot leak from local files. Second, add statement checks that inspect each SQL command before the database runs it. If an agent tries to drop a table, the check can block it. You can also hold write statements until a team lead approves the action. Third, apply data masking to rewrite matched fields like emails or card numbers. Masking rewrites those fields in results while keeping the query format valid. Finally, record every query alongside the user identity that started the agent run.

Check every Postgres query on the wire

Database roles and network rules decide who can open a session. They do not read what each SQL statement does after login. With hoop.dev, you run an open-source proxy, a sidecar for your Postgres. It runs beside your database and reads the Postgres wire protocol. Your apps and agents keep their login details and change only the host and port in the connection string their tool uses.

Before a query runs, hoop.dev guardrails check the statement by its effect, table, or pattern. They refuse bad deletes or drops with a real Postgres error. On the way back, hoop.dev data masking rewrites sensitive values in returned rows based on your rules. Every query and verdict goes to the audit trail. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and generates evidence for HIPAA, GDPR, and PCI DSS. See the code on GitHub.

Frequently asked questions

Should I use the default postgres password for my agent?

No, the default postgres role has admin rights across your project. Always create a separate database user with limited table grants for each external tool.

How do I limit what tables the agent can read?

Create a custom role in your database and revoke default public schema rights. Then grant select privileges only on the specific tables the agent needs to read.

Why is a read-only database role still a risk for agents?

A read-only role still returns raw emails, phone numbers, and card numbers in results. Without field masking, those sensitive values enter the model prompt and local logs.

The query runs. The emails stay hidden.