Skip to main content
Book a demo

Connect Jamf to GitHub Copilot CLI

Give GitHub Copilot CLI governed access to Jamf’s 6 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo GitHub Copilot CLI setup guide

Set up

Add Jamf 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. 1

    Approve Jamf in Runlayer

    Add Jamf from the catalog and choose who can use it and which of its tools are allowed.

  2. 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 Jamf’s 6 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI setup guide
  3. 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. 4

    Use Jamf from GitHub Copilot CLI

    Jamf’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.

Tools

6 Jamf tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI 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 CLI

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Jamf 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

Find another combination