Connect Zip to Codex
Give Codex governed access to Zip’s 65 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Zip to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Add Zip to Runlayer
Zip isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 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, Zip’s 65 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 Zip
Sign in the way Zip requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Zip from Codex
Zip’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
65 Zip tools in Codex
Runlayer policy decides which of these Codex users can call.
Get agreement
Fetch a single agreement (contract) by GUID.
Get attachment
Get a single attachment (document) by GUID.
Get attachment download URL
Get a single-use download URL for the primary (latest) version of an attachment.
Get cash back
Get a single virtual card cash back by GUID.
Get category
Fetch a single taxonomy node (category) by GUID.
Get change order
Get a single change order (purchase requisition of type CHANGE_ORDER) by GUID.
Get context library
Fetch a single context library entry by GUID, including its latest published version (purpose, instructions, version number).
Get credit memo
Get a single credit memo by GUID.
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 Zip 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