Explore Snowflake databases, schemas, and columns, then run SQL as an approved step
Connect Snowflake and the agent can walk your account the way you would: list databases, list schemas, list tables with row counts and sizes, describe columns, and sample distinct values. That context is read on demand, no setup per question. Running SQL is a separate, approved step, so a query only reaches the warehouse once you say so.
6 tools: 5 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Snowflake Basic run looks like inside Luumen.
Authorize once with Basic auth. 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 run query. 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 Snowflake Basic — 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.