Skip to main content
Book a demo

Connect DoorDash to Claude Cowork

Give Claude Cowork governed access to DoorDash’s 32 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude Cowork setup guide

Set up

Add DoorDash to Claude Cowork in four steps

Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.

  1. 1

    Approve DoorDash in Runlayer

    Add DoorDash from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude Cowork to Runlayer

    Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, DoorDash’s 32 tools show up in Claude Cowork’s own tool list.

    Claude Cowork setup guide
  3. 3

    Sign in to DoorDash

    Each user signs in to DoorDash with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use DoorDash from Claude Cowork

    DoorDash’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.

Tools

32 DoorDash tools in Claude Cowork

Runlayer policy decides which of these Claude Cowork 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.

See all 32 DoorDash tools

Control

What Runlayer can see and stop in Claude Cowork

Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.

  • Gateway policy (available)

    Every DoorDash call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.

  • OTLP telemetry (available)

    Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.

In Claude Cowork

  • Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.

Frequently asked questions

Connect more

Find another combination