Connect Ramp to Goose
Give Goose governed access to Ramp’s 124 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ramp to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Ramp in Runlayer
Add Ramp 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 Ramp’s 124 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Ramp
Each user signs in to Ramp with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Ramp from Goose
Ramp’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
124 Ramp tools in Goose
Runlayer policy decides which of these Goose users can call.
Activate card
Activate a card by its last four digits.
Add traveler loyalty program
Compatibility route for callers that have not migrated to SetTravelerLoyaltyProgram.
Answer policy question
Get an answer to a question about the expense policy or funds (amount, restrictions, etc).
Approve or reject bill
Approve or reject a submitted bill that is pending approval.
Approve or reject reimbursement
Approve or reject an employee reimbursement request for an out-of-pocket expense.
Approve or reject request
Approve or reject a pending unified request for spend allocation (fund), purchase order, or procurement approval.
Approve or reject transaction
Approve or reject a transaction awaiting your review.
Cancel reimbursement payment
Cancel the payment on a reimbursement that has been approved but not yet paid out.
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 Ramp 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