Skip to main content
Book a demo

Connect Google Drive to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

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

    Add Google Drive 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 Drive’s 16 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 Drive

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

  4. 4

    Use Google Drive from Cline CLI

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

Tools

16 Google Drive tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call. 5 read data only and 1 can change or delete data.

  • Copy file

    Create a copy of a file in Google Drive.

  • Create doc from markdown

    Create a beautifully formatted Google Doc from markdown content.

  • Create file

    Create a new file in Google Drive with text or base64-encoded content.

  • Create folder

    Create a new folder in Google Drive to organize files.

  • Delete file

    Delete a file or folder by moving it to trash.

  • Fetch file

    Fetch a file from Google Drive using its Google Drive file ID (don't use exa nor brave to read files).

  • Get metadata

    Get detailed metadata about a specific file or folder, including size, ownership, sharing status, modification dates, and more.

  • List folder

    List all files and folders within a specific folder.

See all 16 Google Drive 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 Drive 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