How to Configure Continue MariaDB Sandbox

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a continue mariadb sandbox by linking your editor assistant to a test database. You give the assistant a read-only database role with tight limits. Many teams start by using an admin login for fast local testing. That broad role lets the AI coding tool run unsafe commands by mistake. A stray prompt can drop tables or read private test rows. How to set up a continue mariadb sandbox First, you start an isolated MariaDB instance for your team to test against. This test database should

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 a continue mariadb sandbox by linking your editor assistant to a test database. You give the assistant a read-only database role with tight limits. Many teams start by using an admin login for fast local testing. That broad role lets the AI coding tool run unsafe commands by mistake. A stray prompt can drop tables or read private test rows.

How to set up a continue mariadb sandbox

First, you start an isolated MariaDB instance for your team to test against. This test database should live on a separate network from live user data. Next, you create a dedicated database user just for the coding assistant. You grant this user permission to read schema details and select from safe tables. You do not grant rights to drop tables, change schemas, or manage users.

After the database role is ready, you set up the Continue extension in your editor. The extension uses a context provider or tool protocol to talk to MariaDB. You put the sandbox host, port, and user login into the local settings file. When a developer asks a question, the assistant reads the database schema. It uses those table names to write accurate SQL queries for the app.

Teams also load fake data into the sandbox before running any AI prompts. Still, many teams copy snapshots from live databases into their test setups. Those snapshots often hold real emails, phone numbers, card numbers, and national IDs. You must clean those columns or use a role that blocks sensitive tables.

What native MariaDB roles solve and what they miss

Native MariaDB grants do a good job of blocking broad access at login. If the assistant logs in with a read-only role, it cannot delete rows. You can also limit which schemas and tables that specific account can read. This stops the AI tool from touching admin tables or billing records.

Still, static database grants only check who logs in at the start. They do not inspect what each individual query does while it runs. A read-only account can still run a huge join that locks up the sandbox. It can also pull thousands of rows of sensitive test data into the prompt.

AI Sandbox Environments + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Once those rows enter the editor context, they go to the model provider. Native roles also lack a clear way to approve a single write command. If a developer wants the assistant to test a migration, they must change grants. Teams often leave those wider grants on by mistake after the test ends. Sharing static database passwords in local config files also creates a cleanup problem. When someone leaves the team, you must rotate keys across every developer machine.

Managing AI queries and test data in flight

To close this gap, teams need controls that work on every single query. Instead of giving the editor a raw password, you should verify developer identity first. Each query from the assistant should tie back to a real person on the team. This gives you a clear log of every statement the AI tool runs.

You also need a way to handle sensitive columns during query execution. Data masking rewrites matched fields like emails and card numbers in query results. The assistant gets valid row shapes for coding, while real values stay protected. If the assistant needs to run a schema change, a human can approve that single command.

Check MySQL queries and results on the wire

MySQL grants control who logs in. They do not check single queries or mask sensitive columns once a session starts. With hoop.dev, you run an open-source proxy, a sidecar for your MySQL. It runs next to MySQL, RDS, or Aurora and reads the MySQL wire protocol.

Multi-statement batches and prepared queries are split and checked one by one by hoop.dev guardrails. When a rule refuses a query, MySQL returns a native error packet with your message. On the response path, hoop.dev data masking rewrites string values in returned rows that match your rules. Every query and decision is logged per resource. See the MIT-licensed project on GitHub.

Frequently asked questions

Why should I use a separate MariaDB role for Continue?

A separate role limits what the AI assistant can read or change. If a prompt creates a bad query, tight grants stop it from dropping tables.

How do I keep real user data out of editor prompts?

Use synthetic data in your sandbox whenever you can. If you use real snapshots, apply data masking to rewrite emails, phone numbers, and card numbers.

Can the coding assistant run schema migrations in the sandbox?

Yes, if you allow write commands for that session. It is safest to review and approve each migration query before it runs on the database.

The query runs. The emails stay hidden.