Skip to main content
Book a demo

Connect Drata to Claude

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

Book a demo Claude setup guide

Set up

Add Drata to Claude in four steps

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

  1. 1

    Approve Drata in Runlayer

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

    Claude setup guide
  3. 3

    Sign in to Drata

    Sign in the way Drata requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Drata from Claude

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

Tools

38 Drata tools in Claude

Runlayer policy decides which of these Claude users can call.

  • Create background check

    File a Background Check for a personnel record, evidenced by a URL.

  • Create control

    Create a new compliance control in a workspace.

  • Create evidence

    Register a new evidence bucket in Drata's reusable Evidence Library.

  • Create risk

    Create a new custom risk in a risk register.

  • Create vendor

    Create a new third-party vendor for the account (TPRM).

  • Delete evidence

    Permanently delete an ENTIRE evidence bucket -- the folder AND every file in it, plus all version history and control linkages.

  • Delete evidence artifact

    Permanently delete ONE file from an evidence bucket, including that file's entire version history.

  • Delete risk

    Permanently delete a single risk from a risk register.

See all 38 Drata 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 Drata 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