Connect Rippling to Goose
Give Goose governed access to Rippling’s 1 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Rippling to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Add Rippling to Runlayer
Rippling isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Rippling’s 1 tool through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Rippling
Sign in the way Rippling requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Rippling from Goose
Rippling’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
1 Rippling tools in Goose
Runlayer policy decides which of these Goose users can call.
Code
Async () => {...};never async (codemode).
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 Rippling 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