Skip to main content
Book a demo

Connect Looker to Windsurf

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

Book a demo Windsurf setup guide

Set up

Add Looker to Windsurf in four steps

Admins approve the server once. Everyone in Windsurf 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 Windsurf to Runlayer

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

    Windsurf 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 Windsurf

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

Tools

30 Looker tools in Windsurf

Runlayer policy decides which of these Windsurf 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 Windsurf

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Windsurf 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 Windsurf runs it.

  • Block output after it runs (not available)

    Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.

In Windsurf

  • Enforcement needs Windsurf 1.12.31 or newer.
  • When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.

Frequently asked questions

Connect more

Find another combination