Connect Metabase to Codex
Give Codex governed access to Metabase’s 45 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Metabase to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Metabase in Runlayer
Add Metabase from the catalog and choose who can use it and which of its tools are allowed.
- 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, Metabase’s 45 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex setup guide - 3
Sign in to Metabase
Sign in the way Metabase requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Metabase from Codex
Metabase’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
45 Metabase tools in Codex
Runlayer policy decides which of these Codex users can call. 25 read data only and 6 can change or delete data.
Construct query
Construct a Metabase query from a structured program with source and operations.
Create dashboard
Create a dashboard in Metabase.
Create question
Save a query as a named question in Metabase.
Execute query
Execute a previously constructed query and return the results with column metadata, row count, and execution time.
Get metric
Get details about a metric including its queryable dimensions.
Get metric field values
Get sample values and statistics for a field in a metric.
Get table
Get details about a table including its fields, related tables, and metrics.
Get table field values
Get sample values and statistics for a field in a table.
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 Metabase 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