Skip to main content
Book a demo

Connect Ordinal to Gemini CLI

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

Book a demo Gemini CLI setup guide

Set up

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

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

    Gemini CLI setup guide
  3. 3

    Sign in to Ordinal

    An admin adds Ordinal credentials to Runlayer once. They never sit in the client’s configuration.

  4. 4

    Use Ordinal from Gemini CLI

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

Tools

50 Ordinal tools in Gemini CLI

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

  • Get analytics cpm

    Get CPM Values - Retrieve the current CPM (Cost Per Mille) values used for EMV calculations across all platforms.

  • Update analytics cpm

    Update CPM Values - Update the CPM values used for EMV calculations.

  • Analytics linkedin followers

    Retrieve follower count history for a LinkedIn profile.

  • Analytics linkedin posts

    Retrieve post analytics for a LinkedIn profile within a date range.

  • Analytics x followers

    Retrieve follower count history for an X profile.

  • Analytics x posts

    Retrieve post analytics for an X profile within a date range.

  • Create approvals

    Create one or more approval requests for a post.

  • Delete approvals

    Delete an approval request.

See all 50 Ordinal 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 Ordinal 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