Skip to main content
Book a demo

Connect Plaid to Gemini CLI

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

Book a demo Gemini CLI setup guide

Set up

Add Plaid 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 Plaid to Runlayer

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

    Gemini CLI setup guide
  3. 3

    Sign in to Plaid

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

  4. 4

    Use Plaid from Gemini CLI

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

Tools

5 Plaid tools in Gemini CLI

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

  • Debug item

    Diagnose a Plaid item by retrieving its state information.

  • Get link analytics

    Retrieves Plaid Link analytics data for analyzing user conversion and error rates.

  • Get tools introduction

    Returns a list of all available tools with a brief introduction for each.

  • Get usages

    Retrieves usage metrics for Plaid products and services.

  • List teams

    Retrieve teams associated with the user and present them as a selectable list.

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 Plaid 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