Connect Great Question to Codex
Give Codex governed access to Great Question’s 132 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Great Question to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Add Great Question to Runlayer
Great Question 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, Great Question’s 132 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 Great Question
Sign in the way Great Question requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Great Question from Codex
Great Question’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
132 Great Question tools in Codex
Runlayer policy decides which of these Codex users can call.
Add interview moderator
Add a new interview moderator.
Add interview participant
Add a new interview participant.
Add interview screener Question
Add a new interview screener question.
Add study participant
Add a new study participant.
Add survey participant
Add a new survey participant.
Add survey Question
Add a new survey question.
Add survey screener Question
Add a new survey screener question.
Add unmoderated participant
Add a new unmoderated participant.
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 Great Question 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