How to Configure Make ClickHouse Guardrails
You set up make clickhouse guardrails by giving the automation app a restricted database user. Then you limit that user with SQL roles, column grants, and query quotas. Teams often share one admin account across all their automated workflows to move fast. Broad permissions let a broken workflow drop tables or read sensitive data by mistake. How to set up make clickhouse guardrails with native SQL roles ClickHouse manages users, roles, row policies, settings profiles, and quotas as SQL access
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 make clickhouse guardrails by giving the automation app a restricted database user. Then you limit that user with SQL roles, column grants, and query quotas. Teams often share one admin account across all their automated workflows to move fast. Broad permissions let a broken workflow drop tables or read sensitive data by mistake.
How to set up make clickhouse guardrails with native SQL roles
ClickHouse manages users, roles, row policies, settings profiles, and quotas as SQL access entities. Before creating these rules, an admin must turn on SQL-driven access control. This setup needs a storage directory path and one user with access management turned on. Once active, an admin with the create user privilege makes an account for Make. A user can only grant the privileges that they hold themselves.
When you create the user, you set the login method and allowed host locations. You also attach default roles and user settings to that account. For read tasks, you can grant select access on specific columns in a table. The workflow can then query only those exact columns. If a workflow runs a wildcard select on all columns, the database refuses it. That wildcard query returns no data unless the table holds only the granted columns. You can also use a trailing asterisk to grant access by table name prefix.
Why native permissions leave gaps in automated workflows
Native roles and column grants control who can log in and which objects they touch. They work well when every scenario in your automation tool needs the exact same data. In practice, dozens of different workflows often share one database login inside the automation app. One workflow might sync billing metrics while another sends customer alerts to chat tools.
Static column grants cannot inspect what an individual query does while it runs. If a scenario has select access to a user table, it pulls raw values. It will read emails, phone numbers, card numbers, and national IDs in clear text. Native grants also cannot pause a risky delete or update statement for human approval. You have to choose between blocking a column everywhere or exposing raw data to every workflow.
ClickHouse Access Management + AI Guardrails: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Separating workflow identity from query execution
Good database security needs checks at two levels. First, you keep the native database user locked down to the minimum required tables. You set host limits and settings profiles so the account cannot change its own rules. Second, you inspect individual statements as they travel from the automation platform to the database.
Checking queries in flight lets you apply rules based on the specific statement content. You can block unapproved drop commands even if the shared user holds write privileges. You can also apply data masking to rewrite matched fields in results before Make receives them. This setup keeps emails and card numbers safe while letting automated reports run on time.
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
How do you limit Make to specific ClickHouse columns?
You grant select privileges on named columns in your table to the Make database user. The user can query those columns, while wildcard queries across restricted columns return no data.
What is needed to manage ClickHouse users with SQL?
You must set a storage directory path on the server for access control files. You also need at least one database user with access management privileges turned on.
Can a ClickHouse user grant permissions to another automation role?
A user can only grant the privileges that they hold themselves, plus the required grant option. Creating a new account also requires the create user privilege on the database.
Related guides
In this post