Runlayer for GitHub Copilot

Connect GitHub Copilot-compatible MCP workflows to centralized Runlayer access and policy.

Connect

Give everyone in GitHub Copilot the golden path to approved tools

Add one Runlayer Plugin endpoint so people find every tool they’re approved for, or connect a single server when you want a narrower set.

Runlayer Plugin

Add one remote MCP endpoint. Users discover and authorize the approved tools available to them without accumulating separate client configurations.

Direct connection

Give the client a dedicated Runlayer URL for one connector. Identity, policy, scanning, and audit still stay attached to every request.

Connection support

Remote MCP and local MCP

Observe

Runlayer uses every channel GitHub Copilot exposes. Each one is labeled, so you can tell real-time hooks from after-the-fact imports.

Supported

Runlayer records identity, policy, scanner, and audit activity for MCP requests routed through the gateway.

Enforce

Each row reflects Runlayer’s enforcement code for GitHub Copilot: what it can stop before a call runs, block afterward, or redact in place.

Control	Support	What that means
Pre-tool deny	At the gateway	Runlayer has no hook in GitHub Copilot that can stop a tool call; Runlayer policies stop calls to Runlayer connectors at the gateway.
Post-tool output block	At the gateway	Runlayer has no hook in GitHub Copilot that can block tool output; ToolGuard blocks unsafe output from Runlayer connectors at the gateway.
Output rewrite	At the gateway	Runlayer has no hook in GitHub Copilot that can rewrite tool output; ToolGuard masks sensitive output from Runlayer connectors at the gateway.