Per-role identity
Each Sembric role maps to its own customer service account. The Sembric runtime holds Token Creator on those target accounts only and impersonates the account mapped to the acting role.
Integration · Google Cloud data warehouse
Governed BigQuery access for AI agents
Discover a BigQuery dataset and serve certified aggregates and governed views to agents, with each Sembric role impersonating its own customer service account.
Identity
How Sembric connects to BigQuery
Your policies stay in force
BigQuery row-level and column-level policies stay in force because every query runs as the mapped account. Curated datasets or authorized views keep raw and regulated tables out of reach.
Enforcement
What Sembric checks and refuses
- Discovery pages through the entire dataset and commits a new catalog only after every metadata call succeeds.
- Nested STRUCT and repeated ARRAY fields keep their full type in the reviewed fingerprint, start sensitive when a nested field name looks personal, and can never be measures or dimensions.
- Every result page is read; repeated or missing page tokens are refused, so a partial page is never treated as the whole answer.
- NUMERIC, BIGNUMERIC and wide integers return as exact strings; timestamps return as ISO strings.
- Each job reserves from a workspace UTC-day billed-byte allowance (10 GB by default) before it starts and carries a matching maximumBytesBilled and a 30-second timeout.
Limits
What these controls don’t do
- The billed-byte allowance is an on-demand query control, not an invoice limit: capacity reservations, storage and other Google Cloud charges are outside it. Keep project budgets and billing alerts.
- Only confirmed billed bytes return unused allowance; failed or uncertain jobs keep their full reservation.
Setup
Connecting BigQuery
- Create one service account per Sembric role with metadata and data read on the chosen dataset or authorized views, plus BigQuery Job User on the billing project.
- Grant the Sembric runtime identity Token Creator on those service accounts only. In an isolated customer plane, the connection form shows the exact identity to grant.
- An owner enters the data project, dataset, billing project, location, per-query billed-byte cap and the account for each role, then tests every mapping before saving.
- Discover the dataset, have the asset’s steward review classifications, then define and independently certify products and views.
FAQ
BigQuery questions
Something else? Ask us directly.
Does Sembric need access to all of our BigQuery data?
No. Each role’s service account should read only a curated dataset or authorized views. Sembric discovers what that account can see, and agents can reach only certified surfaces built on reviewed, non-sensitive fields.
Can an agent run up a large BigQuery bill?
Agents cannot send SQL. Every job reserves from a workspace daily billed-byte allowance and carries maximumBytesBilled. That bounds on-demand query bytes, but it is not an invoice limit, so keep project budgets and alerts too.
More sources
Other integrations
Cloud data platform
Snowflake
Connect a Snowflake schema over the SQL API with one key-pair user and role per Sembric role, and let agents query only certified surfaces.
Federated SQL engine and lakehouse catalogs
Trino
Discover one Trino catalog and schema, including a lakehouse catalog you operate, and serve certified surfaces through role-specific read-only users.
Databricks SQL warehouse with Unity Catalog
Databricks
Connect a Databricks SQL warehouse and one Unity Catalog schema with a separate OAuth service principal per Sembric role.
Native PostgreSQL
PostgreSQL
Connect an existing PostgreSQL schema over verified TLS with a restricted login per Sembric role, keeping row-level security in force.
MySQL 8.0 and 8.4
MySQL
Connect a MySQL 8.0 or 8.4 database over mandatory verified TLS with direct read-only grants per Sembric role.
Put your first certified data product in front of an agent.
Tell us which warehouse you run and what your agents need to answer. We will help you connect a source, certify a first surface and query it over MCP.