Skip to main content
Book a demo

Connect Google BigQuery to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Google BigQuery to Cline CLI in four steps

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

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Google BigQuery’s 9 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI 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 Cline CLI

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

Tools

9 Google BigQuery tools in Cline CLI

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Block output after it runs (not available)

    Cline CLI 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)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination