Skip to main content
Book a demo

Connect Carta to Gemini CLI

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

Book a demo Gemini CLI setup guide

Set up

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

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

    Gemini CLI setup guide
  3. 3

    Sign in to Carta

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

  4. 4

    Use Carta from Gemini CLI

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

Tools

18 Carta tools in Gemini CLI

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

  • Call tool

    Run a Carta tool that search_tools found.

  • Cap table chart

    Show a visual cap table summary with ownership breakdown by share class.

  • Discover

    List available Carta commands or views across all domains.

  • Fetch

    Execute a named Carta read command.

  • Get current user

    Get the currently authenticated Carta user's profile.

  • List accounts

    List all companies and organizations the current user has access to.

  • List contexts

    Show which firms you have access to in Carta Fund Admin and which one is currently active.

  • List resources

    List all available resources and resource templates.

See all 18 Carta 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 Carta 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