Connect Perk to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Perk’s 44 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Perk to GitHub Copilot CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.
- 1
Add Perk to Runlayer
Perk isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect GitHub Copilot CLI to Runlayer
Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Perk’s 44 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 3
Sign in to Perk
Sign in the way Perk requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Perk from GitHub Copilot CLI
Perk’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
44 Perk tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI users can call.
Approvals get trip approval links
Get a link the user can open to approve or decline a specific trip.
Cars build car deeplink
Generate a Perk deep-link to the Configure page for a chosen car offer, with that offer preselected, so the user can complete the booking.
Cars get car search results
Fetch available car rental offers for a search.
Cars list car delivery addresses
List the account's car delivery and collection addresses - locations where a rental car can be delivered to and picked up from, instead of a rental office.
Cars search car places
Search for airports, cities, and addresses by name, to resolve the place objects required by start_car_search's pick_up_location/drop_off_location parameters.
Cars start car search
Start a car rental search.
Events create event
Create a new Perk Event.
Events list event attendance
List attendees for a specific Perk Event.
Control
What Runlayer can see and stop in GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every Perk call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot CLI 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 or permission request before GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more