Skip to main content
Book a demo

Connect Google Sheets to VS Code

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

Book a demo VS Code setup guide

Set up

Add Google Sheets 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 Sheets in Runlayer

    Add Google Sheets 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 Sheets’s 21 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 Sheets

    Sign in the way Google Sheets requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Google Sheets from VS Code

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

Tools

21 Google Sheets tools in VS Code

Runlayer policy decides which of these VS Code users can call. 4 read data only and 4 can change or delete data.

  • Add sheet

    Add a new sheet (tab) to an existing spreadsheet.

  • Append

    Append data to a spreadsheet.

  • Autofill

    Extend a formula or detected series from a source range into a larger destination range (like dragging the fill handle).

  • Clear

    Clear the values in a range while leaving the rows, columns, and formatting in place.

  • Clear filter

    Remove a sheet's filter, restoring any rows it was hiding.

  • Create

    Create a new spreadsheet.

  • Create filter

    Turn on filtering over a range of a sheet (the funnel button in the Sheets UI), so rows can be sorted and filtered by column.

  • Delete rows

    Delete rows from a sheet, shifting the rows below them up.

See all 21 Google Sheets 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 Sheets 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