Skip to main content
Book a demo

Connect dbt to Codex

Give Codex governed access to dbt’s 42 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Codex setup guide

Set up

Add dbt to Codex in four steps

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

  1. 1

    Approve dbt in Runlayer

    Add dbt from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Codex to Runlayer

    Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, dbt’s 42 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex setup guide
  3. 3

    Sign in to dbt

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

  4. 4

    Use dbt from Codex

    dbt’s approved tools appear in Codex. Every call is checked against policy and recorded.

Tools

42 dbt tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Cancel job run

    Cancel a currently running or queued dbt run.

  • Get all macros

    Get the name, description, and package name of all dbt macros in the environment.

  • Get all models

    Get the name and description of all dbt models in the environment.

  • Get all sources

    Get the name, description, and metadata of all dbt sources in the environment.

  • Get dimension values

    Get the distinct values for a given dimension, optionally scoped to specific metrics.

  • Get dimensions

    Get the dimensions for specified metrics

  • Get entities

    Get the entities for specified metrics

  • Get exposure details

    DEPRECATED — use get_node_details instead.

See all 42 dbt tools

Control

What Runlayer can see and stop in Codex

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Codex 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 or permission request before Codex runs it.

  • Block output after it runs (available)

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

  • Redact output in place (not available)

    Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination