Skip to main content
Book a demo

Connect Pigment to Gemini CLI

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

Book a demo Gemini CLI setup guide

Set up

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

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

    Gemini CLI setup guide
  3. 3

    Sign in to Pigment

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

  4. 4

    Use Pigment from Gemini CLI

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

Tools

101 Pigment tools in Gemini CLI

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

  • Add list items

    Add one or more new items (rows) to a dimension/list with their property values in a single operation.

  • Batch share blocks

    Share multiple lists and metrics in a single operation, making them visible and usable across applications within the organization.

  • Calendar add time dimension

    Add a new time dimension to existing Application calendar.

  • Create calendar

    Creates a new gregorian calendar in the Pigment application.

  • Calendar expand

    Expands or shrinks a calendar's date range.

  • Get calendar

    Retrieves detailed configuration of a specific calendar.

  • Calendar remove time dimension

    Remove a time dimension from the Application's calendar.

  • Clear widget preview

    Removes the Draft View preview from a single Board widget for the current user, so the widget shows its saved View again.

See all 101 Pigment 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 Pigment 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