Connect Pendo to Gemini CLI
Give Gemini CLI governed access to Pendo’s 54 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Pendo to Gemini CLI in four steps
Admins approve the server once. Everyone in Gemini CLI then gets it through the same governed connection.
- 1
Approve Pendo in Runlayer
Add Pendo from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Gemini CLI to Runlayer
Users add the Runlayer Plugin to Gemini CLI by following Runlayer’s setup guide. Gemini CLI reaches Pendo’s 54 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Gemini CLI setup guide - 3
Sign in to Pendo
Sign in the way Pendo requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Pendo from Gemini CLI
Pendo’s approved tools appear in Gemini CLI. Every call is checked against policy and recorded.
Tools
54 Pendo tools in Gemini CLI
Runlayer policy decides which of these Gemini CLI users can call.
Account metadata schema
Return the set of metadata fields available for accounts.
Acquisition trend
Count new visitors or accounts per period - users whose first-ever interaction with the app (scope='app'), a specific page or feature (scope='page' or 'feature'), or a track event…
Agent analytics conversation analysis
Lists and ranks individual AI agent conversations with per-conversation metrics.
Agent analytics issue analysis
Returns issue diagnoses, flagged response tool/model usage, and user prompt content for the events of a specific detected issue cluster in AI Agent Analytics.
Agent analytics key metrics
Returns key aggregate metrics for AI agent conversations with period-over-period comparison.
Agent analytics tracked issue analysis
Deep-dives into a single tracked issue in AI Agent Analytics for a specific AI agent, surfacing the visitors and accounts, sampled issue explanations from detected issue clusters, the tools and…
Agent analytics tracked use case analysis
Deep-dives into a single tracked use case in AI Agent Analytics for a specific AI agent, surfacing the visitors and accounts, the tools and models the agent invoked, sampled explanations, and a…
Aggregate entity usage
Rank pages, features, or track events by aggregate usage over a date range, or measure a named set of them as one population.
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 Pendo 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