Connect Navattic to Codex
Give Codex governed access to Navattic’s 62 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Navattic to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Add Navattic to Runlayer
Navattic 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, Navattic’s 62 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 Navattic
Sign in the way Navattic requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Navattic from Codex
Navattic’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
62 Navattic tools in Codex
Runlayer policy decides which of these Codex users can call.
Create brain asset
Add a URL, FILE, or TEXT asset to an agent's brain.
Create launchpad share link
Create a launchpad share link, sourced from either a set of custom flows or a demo.
Delete brain asset
Permanently delete a Brain asset.
Get account
Get a detailed profile for a specific company account by ID.
Get agent demo
Get a Navattic agent's configuration — objective, personality, tone, FAQs, pronunciations, CTA, welcome screen, language, voice, avatar, escalation/interruption flags, and the linked environment.
Get agent demo session
Get full details for a Navattic agent session: parsed transcript turns, qualifications, summary, sentiment, signals detected, outcome reached, status, end user, and the Steel session viewer URL for…
Get agent environment
Get an agent environment and its folder/flow tree.
Get demo
Get a specific demo.
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 Navattic 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