Skip to main content

Connect DX Data Cloud to Claude Cowork

Give Claude Cowork governed access to DX Data Cloud’s 10 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add DX Data Cloud 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 DX Data Cloud in Runlayer

    Add DX Data Cloud 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, DX Data Cloud’s 10 tools show up in Claude Cowork’s own tool list.

    Claude Cowork setup guide
  3. 3

    Sign in to DX Data Cloud

    An admin adds DX Data Cloud credentials to Runlayer once. They never sit in the client’s configuration.

  4. 4

    Use DX Data Cloud from Claude Cowork

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

Tools

10 DX Data Cloud tools in Claude Cowork

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

  • Get entity details

    Get comprehensive details about a specific entity including its information, tasks, and scorecards - we can use this to check operational readiness/health of an entity.

  • Get initiative details

    Get initiative details including both the initiative info and its progress report.

  • Get scorecard info

    Retrieve details about a specific scorecard, including its defined levels and checks.

  • Get team details

    Retrieve details for an individual team.

  • List entities

    List entities from the DX software catalog.

  • List initiatives

    Lists all initiatives with summary information.

  • List scorecards

    List all active scorecards.

  • List teams

    List all teams in DX.

See all 10 DX Data Cloud 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 DX Data Cloud 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