Connect Perk to Codex
Give Codex governed access to Perk’s 44 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Perk to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Add Perk to Runlayer
Perk 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, Perk’s 44 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 Perk
Sign in the way Perk requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Perk from Codex
Perk’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
44 Perk tools in Codex
Runlayer policy decides which of these Codex users can call.
Approvals get trip approval links
Get a link the user can open to approve or decline a specific trip.
Cars build car deeplink
Generate a Perk deep-link to the Configure page for a chosen car offer, with that offer preselected, so the user can complete the booking.
Cars get car search results
Fetch available car rental offers for a search.
Cars list car delivery addresses
List the account's car delivery and collection addresses - locations where a rental car can be delivered to and picked up from, instead of a rental office.
Cars search car places
Search for airports, cities, and addresses by name, to resolve the place objects required by start_car_search's pick_up_location/drop_off_location parameters.
Cars start car search
Start a car rental search.
Events create event
Create a new Perk Event.
Events list event attendance
List attendees for a specific Perk Event.
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 Perk 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