Skip to main content
Book a demo

Connect Sigma to Codex

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

Book a demo Codex setup guide

Set up

Add Sigma to Codex in four steps

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

  1. 1

    Add Sigma to Runlayer

    Sigma 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, Sigma’s 7 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 Sigma

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

  4. 4

    Use Sigma from Codex

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

Tools

7 Sigma tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Begin session

    REQUIRED — You MUST call this tool before using any other Sigma tool in a conversation.

  • Call agent

    Call a Sigma workbook agent with a message or conversation.

  • Describe

    Inspect the schema of a Sigma data source.

  • List documents

    Browse a named document collection in the Sigma workspace.

  • List workbook agents

    List the workbook agents you can edit across your organization

  • Query

    Execute a SQL query against a Sigma data source and return the results.

  • Search

    Search across the entire Sigma workspace to discover workbooks, data models, data model elements, and tables.

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