Skip to main content
Book a demo

Connect Datadog to Claude Cowork

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

Book a demo Claude Cowork setup guide

Set up

Add Datadog 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 Datadog in Runlayer

    Add Datadog 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, Datadog’s 414 tools show up in Claude Cowork’s own tool list.

    Claude Cowork setup guide
  3. 3

    Sign in to Datadog

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

  4. 4

    Use Datadog from Claude Cowork

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

Tools

414 Datadog tools in Claude Cowork

Runlayer policy decides which of these Claude Cowork users can call.

  • Dd gff

    Do-not-call

  • Dd guc

    Do-not-call

  • Dd rfw

    Do-not-call

  • Dd wfd

    Do-not-call

  • Aap get activation options

    Aap get activation options.

  • Aap onboarding

    Returns the authoritative step-by-step instructions for enabling Datadog App and API Protection (AAP) to monitor and secure your application.

  • Add comment to Datadog case

    Add a comment to a Datadog Work Item (also called a Case) timeline.

  • Add llmobs annotation queue interactions

    Queue traces, sessions, or spans for human review in an annotation queue.

See all 414 Datadog 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 Datadog 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