Connect Postman to Codex
Give Codex governed access to Postman’s 41 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Postman to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Postman in Runlayer
Add Postman 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, Postman’s 41 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 Postman
Sign in the way Postman requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Postman from Codex
Postman’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
41 Postman tools in Codex
Runlayer policy decides which of these Codex users can call.
Create collection
Creates a collection using the [Postman Collection v2.1.0 schema format](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).
Create collection request
Creates a request in a collection.
Create collection response
Creates a request response in a collection.
Create environment
Creates an environment.
Create mock
Creates a mock server in a collection.
Create spec
Creates an API specification in Postman's [Spec Hub](https://learning.postman.com/docs/design-apis/specifications/overview/).
Create spec file
Creates a file for an OpenAPI or a protobuf 2 or 3 specification.
Create workspace
Creates a new [workspace](https://learning.postman.com/docs/collaborating-in-postman/using-workspaces/creating-workspaces/).
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 Postman 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