Skip to main content
Book a demo

Connect Hex to Goose

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

Book a demo Goose setup guide

Set up

Add Hex to Goose in four steps

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

    Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Hex’s 18 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Goose 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 Goose

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

Tools

18 Hex tools in Goose

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

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

  • Gateway policy (available)

    Every Hex call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Goose 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.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Goose runs it.

  • Block output after it runs (available)

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

  • Redact output in place (not available)

    Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination