Skip to main content

Connect Google Slides to Gemini CLI

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

Set up

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

    Add Google Slides 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 Google Slides’s 28 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Gemini CLI setup guide
  3. 3

    Sign in to Google Slides

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

  4. 4

    Use Google Slides from Gemini CLI

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

Tools

28 Google Slides tools in Gemini CLI

Runlayer policy decides which of these Gemini CLI users can call. 6 read data only and 2 can change or delete data.

  • Add comment

    Add a comment to a Google Slides presentation.

  • Add image

    Add an image to a slide from a URL.

  • Add line

    Add a line or connector to a slide.

  • Add shape

    Add a shape (rectangle, ellipse, etc.) to a slide.

  • Add slide

    Add a new slide to a Google Slides presentation.

  • Add table

    Create a table on a slide with specified rows and columns.

  • Add text

    Add a text box with text to a slide.

  • Create

    Create a new Google Slides presentation.

See all 28 Google Slides 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 Google Slides 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