Connect Salesforce to Gemini CLI
Give Gemini CLI governed access to Salesforce’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Salesforce 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 Salesforce in Runlayer
Add Salesforce 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 Salesforce’s 21 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Gemini CLI setup guide - 3
Sign in to Salesforce
Sign in the way Salesforce requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Salesforce from Gemini CLI
Salesforce’s approved tools appear in Gemini CLI. Every call is checked against policy and recorded.
Tools
21 Salesforce tools in Gemini CLI
Runlayer policy decides which of these Gemini CLI users can call. 7 read data only and 1 can change or delete data.
Create record
Create a new Salesforce record.
Delete record
Delete a Salesforce record by ID.
Describe object
Get detailed metadata for a specific Salesforce sObject including all fields, their types, picklist values, relationships, and constraints.
Get limits
Get the org's API usage limits including daily API calls, data storage, file storage, and other governor limits.
Get record
Retrieve a single Salesforce record by its ID.
List objects
List all sObjects (standard and custom objects) available in the Salesforce org.
Query
Execute a SOQL (Salesforce Object Query Language) query.
Query more
Retrieve the next page of results from a SOQL query.
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 Salesforce 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