Skip to main content

Connect Gmail to Gemini CLI

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

Set up

Add Gmail to Gemini CLI in four steps

Admins approve the server once. Everyone in Gemini CLI then gets it through the same governed connection.

  1. 1

    Approve Gmail in Runlayer

    Add Gmail from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Gemini CLI to Runlayer

    Users add the Runlayer Plugin to Gemini CLI by following Runlayer’s setup guide. Gemini CLI reaches Gmail’s 16 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Gemini CLI setup guide
  3. 3

    Sign in to Gmail

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

  4. 4

    Use Gmail from Gemini CLI

    Gmail’s approved tools appear in Gemini CLI. Every call is checked against policy and recorded.

Tools

16 Gmail tools in Gemini CLI

Runlayer policy decides which of these Gemini CLI users can call. 6 read data only.

  • Add labels

    Add one or more labels to a message or multiple messages

  • Archive messages

    Archive one or more messages (remove from inbox)

  • Create draft

    Create a draft email that can be edited later or sent

  • Create label

    Create a new label in the user's Gmail account

  • Fetch attachment

    Fetch a Gmail message attachment.

  • Fetch message

    Fetch the full content of a Gmail message using its message ID (don't use external tools to read messages)

  • List drafts

    List all draft messages with pagination support

  • List labels

    List all available labels in the Gmail account

See all 16 Gmail tools

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

Find another combination