Skip to main content
Book a demo

Connect Sumble to Codex

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

Book a demo Codex setup guide

Set up

Add Sumble to Codex in four steps

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

  1. 1

    Add Sumble to Runlayer

    Sumble 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, Sumble’s 38 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 Sumble

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

  4. 4

    Use Sumble from Codex

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

Tools

38 Sumble tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Add contacts to list

    Add people to an existing contact list.

  • Add organizations to list

    Add organizations to an existing list.

  • Create contact list

    Create a new contact list (people list).

  • Create organization list

    Create a new organization list.

  • Find match and enrich jobs

    The primary jobs tool: look up jobs by id or search the jobs corpus, and return exactly the attributes you ask for, with optional related people.

  • Find match and enrich organizations

    Find, match, and enrich organizations in one call.

  • Find match and enrich people

    The primary people tool: resolve people and return exactly the attributes you ask for, with optional related people and contact reveals.

  • Find match and enrich teams

    Find the teams inside an organization and return selected attributes, related people, and job postings.

See all 38 Sumble 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 Sumble 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