Cloud SQL
for LuumenAI
Query Cloud SQL state safely; maintenance held for approval.
Bring Cloud SQL state into the investigation: schema, running queries, locks, and replication. Read-only queries show their SQL before running; kills, failovers, and maintenance are held for approval and audited.
The Cloud SQL toolbox
16 tools: 10 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadDescribe schema & objectsTables, indexes, and jobs as context for the investigation.
- ReadRun read-only queryAsk a question of the data with the SQL shown before it runs.
- ReadInspect running queries & locksSee what is slow or blocked right now.
- ReadList databases & tablesWhat exists and how big it is.
- ReadExplain queryThe plan a query will use.
- ReadGet replication statusReplica lag and health.
- ReadList jobs & schedulesPipelines and their next run.
- ReadGet job run logsWhy a job succeeded or failed.
- ReadGet table statsRow counts, growth, and freshness.
- ReadList users & grantsWho can read or write what.
- WriteKill session or jobTerminate a runaway session as an approved action. Approval by default
- WriteRun maintenanceVacuum, reindex, or failover inside a reviewed runbook. Approval by default
- WriteRerun jobRetry a failed run with the same inputs. Approval by default
- WritePause scheduleStop a pipeline from running. Approval by default
- WriteGrant or revoke accessChange a grant as an approved action. Approval by default
- WriteCreate indexAdd an index inside a reviewed change. Approval by default
One prompt, start to finish
What a governed Cloud SQL run looks like inside Luumen.
Questions
Authorize once with Service account. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as kill session or job, run maintenance, rerun job, pause schedule, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Cloud SQL — 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.
Often connected alongside
All integrations
PostgreSQLQuery PostgreSQL state safely; maintenance held for approval.
MySQLQuery MySQL state safely; maintenance held for approval.
Microsoft SQL ServerQuery Microsoft SQL Server state safely; maintenance held for approval.Oracle DatabaseQuery Oracle Database state safely; maintenance held for approval.Put Cloud SQL to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.