Skip to main content
Book a demo

Connect AirOps to Gemini CLI

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

Book a demo Gemini CLI setup guide

Set up

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

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

    Gemini CLI setup guide
  3. 3

    Sign in to AirOps

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

  4. 4

    Use AirOps from Gemini CLI

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

Tools

100 AirOps tools in Gemini CLI

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

  • Accept opportunity

    Accept pending opportunities for a campaign and add them to the campaign action grid.

  • Add AEO region

    Add a region (ISO alpha-2 country code) to a Brand Kit's configured AEO regions.

  • Add grid column

    Add a new column to a grid table.

  • Analytics chart

    Query analytics data and display it as an interactive chart.

  • Automated feedback report

    AirOps only feedback tool.

  • Bulk update AEO prompt tags

    Apply a single tag operation (add or remove) to a batch of AEO prompts in one Brand Kit, atomically.

  • Bulk update AEO prompt topics

    Reassign a batch of AEO prompts to an existing topic in one Brand Kit.

  • Commit AEO prompt assignments

    Commit the current prompt-assignment draft for a Brand Kit to live.

See all 100 AirOps 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 AirOps 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