Connect NetSuite to Goose
Give Goose governed access to NetSuite’s 17 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add NetSuite to Goose in four steps
Admins approve the server once. Everyone in Goose 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 Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches NetSuite’s 17 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose 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 Goose
NetSuite’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
17 NetSuite tools in Goose
Runlayer policy decides which of these Goose 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 Goose
Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.
Gateway policy (available)
Every NetSuite call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Goose 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 Goose runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Goose’s model sees it.
Redact output in place (not available)
Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.
Frequently asked questions
Connect more