Skip to main content
Book a demo

Connect Looker to Gemini CLI

Give Gemini CLI governed access to Looker’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Gemini CLI setup guide

Set up

Add Looker to Gemini CLI in four steps

Admins approve the server once. Everyone in Gemini CLI then gets it through the same governed connection.

  1. 1

    Approve Looker in Runlayer

    Add Looker from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Gemini CLI to Runlayer

    Users add the Runlayer Plugin to Gemini CLI by following Runlayer’s setup guide. Gemini CLI reaches Looker’s 30 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Gemini CLI setup guide
  3. 3

    Sign in to Looker

    Each user signs in to Looker with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Looker from Gemini CLI

    Looker’s approved tools appear in Gemini CLI. Every call is checked against policy and recorded.

Tools

30 Looker tools in Gemini CLI

Runlayer policy decides which of these Gemini CLI users can call.

  • Dev mode

    Allows toggling the Looker IDE session between Development Mode and Production Mode.

  • Generate embed URL

    Generates a signed, private embed URL for specific Looker content, allowing users to access it directly.

  • Get connection databases

    Retrieves a list of databases available through a specified Looker connection.

  • Get connection schemas

    Retrieves a list of database schemas available through a specified Looker connection.

  • Get connection table columns

    Retrieves a list of columns for one or more specified tables within a given database schema and connection.

  • Get connection tables

    Retrieves a list of tables available within a specified database schema through a Looker connection.

  • Get connections

    Retrieves a list of all database connections configured in the Looker system.

  • Get dashboards

    Searches for saved dashboards in a Looker instance.

See all 30 Looker tools

Control

What Runlayer can see and stop in Gemini CLI

Some controls apply to every client at the gateway. Others depend on what Gemini CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Looker call from Gemini CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Gemini CLI as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Gemini CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Gemini CLI’s model sees it.

  • Redact output in place (not available)

    Gemini CLI can only add text to a tool result, not replace it, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

In Gemini CLI

  • Enforcement needs Gemini CLI 0.26.0 or newer.
  • When Runlayer blocks a call or its output, Gemini CLI shows the model the block reason instead.

Frequently asked questions

Connect more

Find another combination