Skip to main content
Book a demo

Connect Google Drive to Claude

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

Book a demo Claude setup guide

Set up

Add Google Drive to Claude in four steps

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

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Google Drive’s 16 tools show up in Claude’s own tool list.

    Claude 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 Claude

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

Tools

16 Google Drive tools in Claude

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

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

  • Gateway policy (available)

    Every Google Drive call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination