Skip to main content
Book a demo

Connect NetSuite to Codex

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

Book a demo Codex setup guide

Set up

Add NetSuite to Codex in four steps

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

  1. 1

    Approve NetSuite in Runlayer

    Add NetSuite 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, NetSuite’s 17 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 NetSuite

    Each user signs in to NetSuite with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use NetSuite from Codex

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

Tools

17 NetSuite tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Ns create record

    Create a new record in NetSuite.

  • Ns get accounting books

    Returns all accounting books available to the user for report execution.

  • Ns get accounting contexts

    Returns all accounting contexts available to the user for report execution.

  • Ns get nexus IDS

    Returns all nexus IDs available to the user for report execution.

  • Ns get record

    Retrieve a record from NetSuite.

  • Ns get record type metadata

    Get metadata information about all record types or from a specific record type including available fields and their types

  • Ns get subsidiaries

    Returns all the subsidiaries available to the user for the report tool.

  • Ns get suite ql metadata

    Retrieves SuiteQL metadata for either all record types list or a specific record type and should be called before runCustomSuiteQL to discover which fields you can safely select, filter, and sort on.

See all 17 NetSuite 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 NetSuite 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