Skip to main content
Book a demo

Connect Runlayer to Gemini CLI

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

Book a demo Gemini CLI setup guide

Set up

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

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

    Gemini CLI setup guide
  3. 3

    Sign in to Runlayer

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

  4. 4

    Use Runlayer from Gemini CLI

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

Tools

139 Runlayer tools in Gemini CLI

Runlayer policy decides which of these Gemini CLI users can call.

  • Add agent connectors

    Add or update connectors on an agent (incremental edit).

  • Add agent skills

    Add skills to an agent (incremental edit).

  • Add agent subagent

    Add one subagent to an existing agent.

  • Add AI watch enforce entry

    Put one source in an Enforce allowlist or Protect denylist.

  • Add plugin connectors

    Add or update connectors on a plugin (incremental edit).

  • Add plugin skills

    Add skills to a plugin (incremental edit).

  • Create agent

    Create a new agent.

  • Create agent eval

    Create an offline eval run: replay selected past agent runs, optionally with overrides, and judge the replays.

See all 139 Runlayer 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 Runlayer 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