Connect Scanner to Codex
Give Codex governed access to Scanner’s 3 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Scanner to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Scanner in Runlayer
Add Scanner 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 Scanner, which runs on the user’s machine. Auto Sync can then write Scanner into Codex on macOS, Windows, and Linux.
Codex setup guide - 3
Sign in to Scanner
An admin adds Scanner credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Scanner from Codex
Scanner’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
3 Scanner tools in Codex
Runlayer policy decides which of these Codex users can call. 3 read data only.
Get Scanner context
Get context about available Scanner indexes and data sources for investigation
Execute query
Execute a search query against Scanner security data lake indexes
Fetch query results
Fetch results from a previously executed Scanner query
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 Scanner 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