Connect Jamf to Codex
Give Codex governed access to Jamf’s 6 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Jamf to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Jamf in Runlayer
Add Jamf 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, Jamf’s 6 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 Jamf
Sign in the way Jamf requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Jamf from Codex
Jamf’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
6 Jamf tools in Codex
Runlayer policy decides which of these Codex users can call.
Execute request
Executes an API request with a given HAR request object.
Get endpoint
Gets detailed information about a specific API endpoint, including security schemes and servers
Get server variables
Gets the server variables for each server within a specific OpenAPI spec.
List endpoints
Lists all API paths and their HTTP methods with summaries, organized by path.
List specs
Lists all available OpenAPI specs.
Search endpoints
Performs a deep search through paths, operations, and parameters to discover relevant API endpoints.
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 Jamf 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