Connect DX Data Cloud to Codex
Give Codex governed access to DX Data Cloud’s 10 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add DX Data Cloud to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve DX Data Cloud in Runlayer
Add DX Data Cloud 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, DX Data Cloud’s 10 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 DX Data Cloud
An admin adds DX Data Cloud credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use DX Data Cloud from Codex
DX Data Cloud’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
10 DX Data Cloud tools in Codex
Runlayer policy decides which of these Codex users can call.
Get entity details
Get comprehensive details about a specific entity including its information, tasks, and scorecards - we can use this to check operational readiness/health of an entity.
Get initiative details
Get initiative details including both the initiative info and its progress report.
Get scorecard info
Retrieve details about a specific scorecard, including its defined levels and checks.
Get team details
Retrieve details for an individual team.
List entities
List entities from the DX software catalog.
List initiatives
Lists all initiatives with summary information.
List scorecards
List all active scorecards.
List teams
List all teams in DX.
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 DX Data Cloud 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