How to Configure Make ClickHouse Sandbox

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a make clickhouse sandbox by creating a restricted database user for your Make scenarios. Then you assign read-only roles and column limits to that account. Many teams connect Make using a shared admin login to save time during testing. That shortcut exposes live tables to accidental writes and leaks sensitive customer records into third-party workflow logs. How to set up a make clickhouse sandbox with native SQL roles ClickHouse manages users, roles, row policies, settings profile

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 make clickhouse sandbox by creating a restricted database user for your Make scenarios. Then you assign read-only roles and column limits to that account. Many teams connect Make using a shared admin login to save time during testing. That shortcut exposes live tables to accidental writes and leaks sensitive customer records into third-party workflow logs.

How to set up a make clickhouse sandbox with native SQL roles

ClickHouse manages users, roles, row policies, settings profiles, and quotas through SQL access control. To turn this on, your server needs a storage path for access files. You also need at least one admin user with access management turned on. Remember that a database user can only grant permissions that they already hold themselves.

Once SQL access control is active, an admin creates a dedicated account for Make. Creating this account requires the create user privilege on the server. During creation, you set the login method and pick the default roles. You also restrict which client hosts can log in with this specific account. For a sandbox, you point this account to test tables or a staging database.

Next, you lock down what the Make scenario can read. ClickHouse lets you grant select permissions on individual columns instead of whole tables. If you grant access to just two columns, queries on other columns will fail. A query that asks for all columns at once will also fail and return nothing. It only works if the table holds just the allowed columns. In ClickHouse 24.10 and newer, you can also grant permissions by table name prefix. A trailing asterisk lets you cover a group of sandbox tables in one rule.

What native sandbox permissions solve and where they fall short

Native roles and column grants stop Make from reading unauthorized tables or dropping data. Host rules also block logins from unknown networks. These tools are great for deciding who can log into the database.

ClickHouse Access Management + AI Sandbox Environments: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Still, static roles cannot inspect what an individual query does while it runs. Make scenarios often pass variables from webhooks straight into database queries. If a column holds mixed data, a static grant lets all of it through. Emails, phone numbers, card numbers, and national IDs then flow into your Make execution history. Updating column grants across dozens of tables as schemas change also takes constant manual work. When a team needs temporary write access for a test, revoking that role later is easy to forget.

Managing automated workflow queries in flight

Safe automation needs controls that look at queries and results in real time. Instead of maintaining complex column grants for every test scenario, teams can filter results dynamically. Dynamic data masking rewrites matched fields like emails or card numbers in query results before Make receives them. Pairing query checks with approval steps also stops risky writes before they hit the database. This keeps your sandbox fast to build and safe for external automation tools.

Check ClickHouse queries and result columns on the wire

ClickHouse users and row policies decide who connects. They do not check each statement on the wire or redact sensitive string columns in query results. With hoop.dev, you run an open-source proxy, a sidecar for your ClickHouse. It reads ClickHouse's native TCP protocol before queries run while ClickHouse stays in charge of login and grants.

Multi-statement queries and table mutations are split and checked by hoop.dev guardrails. Banned actions are refused with a native ClickHouse error. On returned rows, hoop.dev data masking rewrites String and FixedString columns that match your rules. The audit trail logs each query, table, and verdict. See the MIT-licensed source on GitHub.

Frequently asked questions

Why did my select all query fail in the ClickHouse sandbox?

When a user only has select access on specific columns, ClickHouse blocks select all queries. You must name the allowed columns directly in your Make query unless the table has no other columns.

How do I grant a Make user access to multiple sandbox tables at once?

Starting in ClickHouse 24.10, you can use a trailing asterisk on a table name prefix. This lets you grant select permissions across all tables that start with your sandbox prefix.

What server settings are required to manage ClickHouse sandbox users with SQL?

You must configure the access control path directory on the server. You also need an initial user account with access management and named collection control set to one.

The query runs. The emails stay hidden.