Connect Neon to Codex
Give Codex governed access to Neon’s 29 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Neon to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Neon in Runlayer
Add Neon 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, Neon’s 29 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 Neon
Sign in the way Neon requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Neon from Codex
Neon’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
29 Neon tools in Codex
Runlayer policy decides which of these Codex users can call.
List projects
Lists the first 10 Neon projects in your account.
List organizations
Lists all organizations that the current user has access to.
List shared projects
Lists projects that have been shared with the current user.
Create project
Create a new Neon project.
Delete project
Delete a Neon project
Describe project
Describes a Neon project
Run SQL
Execute a single SQL statement against a Neon database.
Run SQL transaction
Execute a SQL transaction against a Neon database, should be used for multiple SQL statements.
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 Neon 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