Skip to main content
Book a demo

Connect RunReveal to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add RunReveal to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.

  1. 1

    Add RunReveal to Runlayer

    RunReveal isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches RunReveal’s 53 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to RunReveal

    Sign in the way RunReveal requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use RunReveal from GitHub Copilot

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

Tools

53 RunReveal tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call.

  • List agent resources

    List built-in reference documents available to load with AgentResourcesLoad.

  • Agent resources load

    Load a built-in reference document by uri.

  • Create agent skills

    Create a new agent skill in this workspace.

  • List agent skills

    List the agent skills available in this workspace.

  • Agent skills load

    Load a single agent skill by name.

  • Update agent skills

    Apply a partial edit to an existing agent skill.

  • Create agents

    Create a scheduled AI agent that runs a prompt on a cron schedule.

  • Delete agents

    Delete a scheduled AI agent by id, including its auto-created role and access policies.

See all 53 RunReveal tools

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 RunReveal 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

Find another combination