Skip to main content
Book a demo

Connect Box to Gemini CLI

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

Book a demo Gemini CLI setup guide

Set up

Add Box 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 Box in Runlayer

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

    Gemini CLI setup guide
  3. 3

    Sign in to Box

    Each user signs in to Box with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Box from Gemini CLI

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

Tools

35 Box tools in Gemini CLI

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

  • Add items to hub

    Adds files, folders, or web links to a specific hub, enabling content organization within collaborative workspaces.

  • Copy file

    Copies an existing file to a destination folder in Box (see Box API Copy file).

  • Copy folder

    Copies an existing folder to a destination parent folder in Box (see Box API Copy folder).

  • Copy hub

    Creates a copy of an existing Box Hub via the Hubs v3 API (POST /v3/hubs/{id}:copy).

  • Create file comment

    Creates a new comment on a specific file.

  • Create folder

    Creates new folders in Box.

  • Create hub

    Creates new collaborative hubs for organizing content around specific topics, projects, or teams.

  • Create metadata template

    Creates a new enterprise metadata template.

See all 35 Box 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 Box 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