Connect Google Drive to Gemini CLI
Give Gemini CLI governed access to Google Drive’s 16 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Google Drive to Gemini CLI in four steps
Admins approve the server once. Everyone in Gemini CLI then gets it through the same governed connection.
- 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
Connect Gemini CLI to Runlayer
Users add the Runlayer Plugin to Gemini CLI by following Runlayer’s setup guide. Gemini CLI reaches Google Drive’s 16 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Gemini CLI setup guide - 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
Use Google Drive from Gemini CLI
Google Drive’s approved tools appear in Gemini CLI. Every call is checked against policy and recorded.
Tools
16 Google Drive tools in Gemini CLI
Runlayer policy decides which of these Gemini 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.
Control
What Runlayer can see and stop in Gemini CLI
Some controls apply to every client at the gateway. Others depend on what Gemini CLI exposes to Runlayer.
Gateway policy (available)
Every Google Drive call from Gemini CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Gemini 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 Gemini CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Gemini CLI’s model sees it.
Redact output in place (not available)
Gemini CLI can only add text to a tool result, not replace it, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.
In Gemini CLI
- Enforcement needs Gemini CLI 0.26.0 or newer.
- When Runlayer blocks a call or its output, Gemini CLI shows the model the block reason instead.
Frequently asked questions
Connect more