Connect NetSuite to VS Code
Give VS Code governed access to NetSuite’s 17 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add NetSuite to VS Code in four steps
Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.
- 1
Approve NetSuite in Runlayer
Add NetSuite from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect VS Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, NetSuite’s 17 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code setup guide - 3
Sign in to NetSuite
Each user signs in to NetSuite with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use NetSuite from VS Code
NetSuite’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
17 NetSuite tools in VS Code
Runlayer policy decides which of these VS Code 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.
Control
What Runlayer can see and stop in VS Code
Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.
Gateway policy (available)
Every NetSuite call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, VS Code 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 VS Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before VS Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.
Frequently asked questions
Connect more