Connect NetSuite to Claude
Give Claude governed access to NetSuite’s 17 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add NetSuite to Claude in four steps
Admins approve the server once. Everyone in Claude 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 Claude to Runlayer
Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, NetSuite’s 17 tools show up in Claude’s own tool list.
Claude 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 Claude
NetSuite’s approved tools appear in Claude. Every call is checked against policy and recorded.
Tools
17 NetSuite tools in Claude
Runlayer policy decides which of these Claude 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 Claude
Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.
Gateway policy (available)
Every NetSuite call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
Compliance API import (available)
Anthropic Compliance API imports Claude web and desktop chats for review.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Stop a call before it runs (available)
Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.
Frequently asked questions
Connect more