Connect Ramp to Cursor
Give Cursor governed access to Ramp’s 124 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ramp to Cursor in four steps
Admins approve the server once. Everyone in Cursor 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 Cursor to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Ramp’s 124 tools show up in Cursor’s own tool list.
Cursor 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 Cursor
Ramp’s approved tools appear in Cursor. Every call is checked against policy and recorded.
Tools
124 Ramp tools in Cursor
Runlayer policy decides which of these Cursor 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 Cursor
Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.
Gateway policy (available)
Every Ramp call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Cursor 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 Cursor runs it, including calls to MCP servers.
Block output after it runs (available)
Runlayer can block a tool’s output before Cursor’s model sees it.
Redact output in place (not available)
Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
In Cursor
- Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
- The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.
Frequently asked questions
Connect more