Skip to main content
Book a demo

Connect Metaview to Codex

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

Book a demo Codex setup guide

Set up

Add Metaview to Codex in four steps

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

  1. 1

    Approve Metaview in Runlayer

    Add Metaview from the catalog and choose who can use it and which of its tools are allowed.

  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, Metaview’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 Metaview

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

  4. 4

    Use Metaview from Codex

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

Tools

53 Metaview tools in Codex

Runlayer policy decides which of these Codex users can call. 11 read data only.

  • Create AI field

    Create a new AI field, or update an existing one (pass field_id).

  • Create report

    Create a new saved report, or update an existing one (pass report_id), in the Metaview web-app.

  • Create snippet

    Save ONE clip of a conversation as a snippet and return links to it.

  • Enrich candidate contacts

    Enrich email addresses or phone numbers for one or more candidates.

  • Fetch candidates

    Look up people/candidates and get, per candidate: profile (professional background — experience, education, skills, location; resolved from a LinkedIn URL, given or found in ATS data) and ats…

  • Find candidate's sequences

    Check if a candidate is enrolled in any sequences — including sequences created by other users.

  • Generate notes

    Generate (or regenerate) AI Notes for a conversation, optionally with a specific built-in or custom template — including to preview how a newly created or updated template renders on a real…

  • Get application review details

    Get the full state of one Application Review: the ACTIVE ICP, any pending DRAFT edit, the RANKING version if a rerank is running, version history, a decision summary, and the fit-band distribution of…

See all 53 Metaview 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 Metaview 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