Skip to main content
Book a demo

Connect Hex to Claude

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

Book a demo Claude setup guide

Set up

Add Hex to Claude in four steps

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

  1. 1

    Approve Hex in Runlayer

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

    Claude setup guide
  3. 3

    Sign in to Hex

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

  4. 4

    Use Hex from Claude

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

Tools

18 Hex tools in Claude

Runlayer policy decides which of these Claude users can call.

  • Continue thread

    Continue a Hex Thread by adding a new message and triggering the agent to process it.

  • Create cell

    Create a new cell in the draft version of a project.

  • Create project

    Create a new project in the workspace with the specified title, and optionally a description.

  • Create thread

    Create a new Hex Thread to ask a question about your data.

  • Delete cell

    Delete a cell from the draft version of a project by ID

  • Get cell

    Get a single cell by ID

  • Get cell image

    Get the rendered PNG image of a chart cell, returned as an image.

  • Get cell output

    Get the latest output preview for a SQL cell in the active draft notebook session.

See all 18 Hex 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 Hex 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