Read BigQuery jobs, schemas, and datasets, then make changes as approved steps
Connect Google BigQuery and your team can ask about a warehouse instead of clicking through the console. Luumen reads job state, query results, table schemas, dataset metadata, connections, and IAM policies on request. Changes — creating a dataset or connection, canceling a running job — are previewed first and, by default, wait for your approval.
62 tools: 33 read, 29 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Google BigQuery run looks like inside Luumen.
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — cancel bigquery job, create capacity commitment, create bigquery connection, create analytics hub data exchange, and more — is shown as a plan and requires approval by default, including the 6 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Google BigQuery — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.