Connect Drata to Codex
Give Codex governed access to Drata’s 38 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Drata to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Drata in Runlayer
Add Drata 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, Drata’s 38 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 Drata
Sign in the way Drata requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Drata from Codex
Drata’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
38 Drata tools in Codex
Runlayer policy decides which of these Codex users can call.
Create background check
File a Background Check for a personnel record, evidenced by a URL.
Create control
Create a new compliance control in a workspace.
Create evidence
Register a new evidence bucket in Drata's reusable Evidence Library.
Create risk
Create a new custom risk in a risk register.
Create vendor
Create a new third-party vendor for the account (TPRM).
Delete evidence
Permanently delete an ENTIRE evidence bucket -- the folder AND every file in it, plus all version history and control linkages.
Delete evidence artifact
Permanently delete ONE file from an evidence bucket, including that file's entire version history.
Delete risk
Permanently delete a single risk from a risk register.
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 Drata 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