Skip to main content
Book a demo

Connect Sanity to Gemini CLI

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

Book a demo Gemini CLI setup guide

Set up

Add Sanity 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

    Add Sanity to Runlayer

    Sanity isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Gemini CLI to Runlayer

    Users add the Runlayer Plugin to Gemini CLI by following Runlayer’s setup guide. Gemini CLI reaches Sanity’s 55 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Gemini CLI setup guide
  3. 3

    Sign in to Sanity

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

  4. 4

    Use Sanity from Gemini CLI

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

Tools

55 Sanity tools in Gemini CLI

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

  • Get UI context

    Returns UI enrichment data for widgets.

  • Add cors origin

    Adds CORS origin(s) to allow client-side requests to a Sanity project

  • Assets upload status

    Retrieve the status and result of your asset upload by operationId.

  • Delete cors origins

    Deletes a CORS origin from a Sanity project

  • List cors origins

    Lists all CORS origins configured for a Sanity project

  • Create dataset

    Creates a new dataset with specified name and access settings

  • Create documents

    Create one or more draft documents by directly providing structured content.

  • Create project

    Creates a new Sanity project and initializes it with a dataset and API tokens

See all 55 Sanity 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 Sanity 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