Connect Ramp to VS Code
Give VS Code governed access to Ramp’s 124 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ramp 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 Ramp in Runlayer
Add Ramp 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, Ramp’s 124 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code 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 VS Code
Ramp’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
124 Ramp tools in VS Code
Runlayer policy decides which of these VS Code 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 VS Code
Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.
Gateway policy (available)
Every Ramp 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