Skip to main content
Book a demo

Connect Drata to Claude Code

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

Book a demo Claude Code setup guide

Set up

Add Drata to Claude Code in four steps

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

    Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, Drata’s 38 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code 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 Code

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

Tools

38 Drata tools in Claude Code

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Anthropic inference hooks (available)

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

  • OTLP telemetry (available)

    Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Claude Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Claude Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.

In Claude Code

  • When a tool fails, Runlayer records the error but cannot hide it.

Frequently asked questions

Connect more

Find another combination