Connect Socket to Codex
Give Codex governed access to Socket’s 1 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Socket to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Socket in Runlayer
Add Socket from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Codex to Runlayer
Install the Runlayer CLI so Codex can reach Socket, which runs on the user’s machine. Auto Sync can then write Socket into Codex on macOS, Windows, and Linux.
Codex setup guide - 3
Sign in to Socket
An admin adds Socket credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Socket from Codex
Socket’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
1 Socket tools in Codex
Runlayer policy decides which of these Codex users can call. 1 read data only.
Depscore
Query dependency security scores across npm, PyPI, cargo, and other package ecosystems.
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 Socket 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