Skip to main content
Book a demo

Connect RunReveal to Codex

Give Codex governed access to RunReveal’s 53 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Codex setup guide

Set up

Add RunReveal to Codex in four steps

Admins approve the server once. Everyone in Codex then gets it through the same governed connection.

  1. 1

    Add RunReveal to Runlayer

    RunReveal isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 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, RunReveal’s 53 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex setup guide
  3. 3

    Sign in to RunReveal

    Sign in the way RunReveal requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use RunReveal from Codex

    RunReveal’s approved tools appear in Codex. Every call is checked against policy and recorded.

Tools

53 RunReveal tools in Codex

Runlayer policy decides which of these Codex users can call.

  • List agent resources

    List built-in reference documents available to load with AgentResourcesLoad.

  • Agent resources load

    Load a built-in reference document by uri.

  • Create agent skills

    Create a new agent skill in this workspace.

  • List agent skills

    List the agent skills available in this workspace.

  • Agent skills load

    Load a single agent skill by name.

  • Update agent skills

    Apply a partial edit to an existing agent skill.

  • Create agents

    Create a scheduled AI agent that runs a prompt on a cron schedule.

  • Delete agents

    Delete a scheduled AI agent by id, including its auto-created role and access policies.

See all 53 RunReveal tools

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 RunReveal 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

Find another combination