Connect Jamf to GitHub Copilot
Give GitHub Copilot governed access to Jamf’s 6 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Jamf to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.
- 1
Approve Jamf in Runlayer
Add Jamf from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot to Runlayer
GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Jamf’s 6 tools through the plugin’s search and execute tools.
GitHub Copilot setup guide - 3
Sign in to Jamf
Sign in the way Jamf requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Jamf from GitHub Copilot
Jamf’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
6 Jamf tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot users can call.
Execute request
Executes an API request with a given HAR request object.
Get endpoint
Gets detailed information about a specific API endpoint, including security schemes and servers
Get server variables
Gets the server variables for each server within a specific OpenAPI spec.
List endpoints
Lists all API paths and their HTTP methods with summaries, organized by path.
List specs
Lists all available OpenAPI specs.
Search endpoints
Performs a deep search through paths, operations, and parameters to discover relevant API endpoints.
Control
What Runlayer can see and stop in GitHub Copilot
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every Jamf call from GitHub Copilot 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 as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more