Skip to main content

Connect DX Data Cloud to Claude

Give Claude 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 in four steps

Admins approve the server once. Everyone in Claude 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 to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, DX Data Cloud’s 10 tools show up in Claude’s own tool list.

    Claude 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

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

Tools

10 DX Data Cloud tools in Claude

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

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

  • Gateway policy (available)

    Every DX Data Cloud call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

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

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude 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)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination