Runlayer for GitHub Copilot CLI

Use approved MCPs from GitHub Copilot CLI with hook-based enforcement and session visibility.

Connect

Give everyone in GitHub Copilot CLI 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 CLI exposes. Each one is labeled, so you can tell real-time hooks from after-the-fact imports.

Supported

Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

Enforce

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

Control	Support	What that means
Pre-tool deny	Supported	Runlayer can deny a tool call or permission request before GitHub Copilot CLI runs it.
Post-tool output block	Supported	Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Output rewrite	Supported	Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.