Connect Gem to Codex
Give Codex governed access to Gem’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Gem to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Add Gem to Runlayer
Gem 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, Gem’s 15 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 Gem
Sign in the way Gem requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Gem from Codex
Gem’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
15 Gem tools in Codex
Runlayer policy decides which of these Codex users can call.
Get application
Look up one application (a candidate on a specific job) by ext_id — status, stage, stage_entry, gem_status (the Talent Pipeline's computed next-step status and SLA health, e.g. NEEDS_DECISION /…
Get job
Look up one job by ext_id — title, status, requisition id, ATS, department/office, and link.
Get metrics catalog
List the metrics and dimensions this team can report on with query_metrics.
Get person
Look up one candidate by ext_id — name, current title, company, school, emails, phone numbers, and links, plus optional fields (full work history, education, custom fields, applications, activity…
Get project
Look up one project by ext_id — name, description, owner, link, type, privacy, archived status, and people_count (candidates in the project).
Get saved report
Look up one saved analytics report (Pipeline Analytics or Outreach) by ext_id — its name, type, owner, link, and a ready-to-run query_metrics payload translated from the report's saved configuration.
Get sequence
Look up one outreach sequence by ext_id — name, status, whether it is a reusable template (is_template) and whether it is archived (is_archived), owner, link, a version (the sequence's edit version —…
Get sequence tokens
List the merge tokens available for writing a sequence stage's subject or body on this team.
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 Gem 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