Skip to main content
Book a demo

Connect Google BigQuery to Windsurf

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

Book a demo Windsurf setup guide

Set up

Add Google BigQuery to Windsurf in four steps

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

  1. 1

    Approve Google BigQuery in Runlayer

    Add Google BigQuery 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 Google BigQuery’s 9 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Windsurf setup guide
  3. 3

    Sign in to Google BigQuery

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

  4. 4

    Use Google BigQuery from Windsurf

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

Tools

9 Google BigQuery tools in Windsurf

Runlayer policy decides which of these Windsurf users can call.

  • Cancel job

    Cancel a running BigQuery job.

  • Execute SQL

    Run a SQL query in the project and return the result.

  • Execute SQL readonly

    Run a read-only SQL query in the project and return the result.

  • Get dataset info

    Get metadata information about a BigQuery dataset or BigLake namespace.

  • Get job

    Get information and status about a BigQuery job.

  • Get query results

    Get the results of a BigQuery SQL query job.

  • Get table info

    Get metadata information about a BigQuery table or BigLake table.

  • List dataset IDS

    List BigQuery dataset IDs and BigLake namespaces in a Google Cloud project.

See all 9 Google BigQuery 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 Google BigQuery 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