Connect Clay to Codex
Give Codex governed access to Clay’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Clay to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Clay in Runlayer
Add Clay 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, Clay’s 21 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 Clay
Sign in the way Clay requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Clay from Codex
Clay’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
21 Clay tools in Codex
Runlayer policy decides which of these Codex users can call. 12 read data only and 3 can change or delete data.
Add company data points
Add data points to companies in an existing search.
Add contact data points
Add data points to contacts in an existing search.
Ask question about accounts
Ask a natural language question about one or more accounts available in Clay Audiences.
Find and enrich company
Find and enrich a single company by domain or LinkedIn URL.
Find and enrich contacts at company
Search for contacts at a company by role, title, name, or department.
Find and enrich list of contacts
Find and enrich specific named contacts at their companies.
Get credits available
Check if credits are available for the workspace.
Get current workspace
Report which Clay workspace this connection is pinned to.
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 Clay 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