Skip to main content
Book a demo

Connect NetSuite to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add NetSuite to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI 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 Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches NetSuite’s 17 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI 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 Cline CLI

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

Tools

17 NetSuite tools in Cline CLI

Runlayer policy decides which of these Cline CLI 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 Cline CLI

Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.

  • Gateway policy (available)

    Every NetSuite call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI 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 before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination