Skip to main content
Book a demo

Connect Google BigQuery to VS Code

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

Book a demo VS Code setup guide

Set up

Add Google BigQuery to VS Code in four steps

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

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Google BigQuery’s 9 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code 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 VS Code

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

Tools

9 Google BigQuery tools in VS Code

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

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

  • Gateway policy (available)

    Every Google BigQuery call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

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

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination