Connect DoorDash to Hermes
Give Hermes governed access to DoorDash’s 32 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add DoorDash to Hermes in four steps
Admins approve the server once. Everyone in Hermes 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 Hermes to Runlayer
Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches DoorDash’s 32 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Hermes 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 Hermes
DoorDash’s approved tools appear in Hermes. Every call is checked against policy and recorded.
Tools
32 DoorDash tools in Hermes
Runlayer policy decides which of these Hermes 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 Hermes
Some controls apply to every client at the gateway. Others depend on what Hermes exposes to Runlayer.
Gateway policy (available)
Every DoorDash call from Hermes passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Hermes 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 Hermes runs it.
Block output after it runs (available)
Runlayer can block a tool’s output in Hermes and show a message in its place.
Redact output in place (not available)
Hermes cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
In Hermes
- Hermes can replace blocked tool output with a message, but its after-call event is for monitoring only.
Frequently asked questions
Connect more
