Connect DoorDash to Gemini CLI
Give Gemini CLI governed access to DoorDash’s 32 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add DoorDash 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 DoorDash in Runlayer
Add DoorDash 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 DoorDash’s 32 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Gemini CLI setup guide - 3
Sign in to DoorDash
Each user signs in to DoorDash with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use DoorDash from Gemini CLI
DoorDash’s approved tools appear in Gemini CLI. Every call is checked against policy and recorded.
Tools
32 DoorDash tools in Gemini CLI
Runlayer policy decides which of these Gemini CLI users can call. 10 read data only.
Get meal manager calendars
List the corporate Meal Manager (DoorDash for Work) calendars the authenticated consumer has access to, and the dated group carts on each one.
Add to cart
Add items from a restaurant's menu to the consumer's cart, creating or updating the cart.
List delivery addresses
Get all saved delivery addresses for the authenticated consumer.
Set delivery address
Set the default delivery address for the authenticated consumer.
Find address
First step of adding a NEW delivery address: resolve a free-text street address into concrete candidates for the user to confirm.
Save address
Second step of adding a NEW delivery address: save the address the user confirmed (by place_id from a prior find_address result).
Get cart
Retrieve the consumer's cart.
Remove cart item
Remove a specific item from the consumer's cart.
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 DoorDash 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
