Connect Wiz to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Wiz’s 238 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Wiz 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
Add Wiz to Runlayer
Wiz isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 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 Wiz’s 238 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 3
Sign in to Wiz
Sign in the way Wiz requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Wiz from GitHub Copilot CLI
Wiz’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
238 Wiz tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI users can call.
AWS organizations overview
Run a structured AWS cloud security assessment against a Wiz environment focused on AWS Organization concepts.
Code to cloud attack path skill
Production vulnerability tracing through deployment pipelines to source code and ownership.
Cost spike investigation skill
Cloud cost anomaly investigation for daily, weekly, or monthly spikes.
Dev documentation search
Searches the Wiz Integration Network (WIN) developer documentation (docs.wiz.io/dev) and returns relevant information and links.
Devops resource auditing skill
Security posture assessment for cloud resources experiencing operational anomalies (CPU spikes, memory issues, network anomalies, cost increases).
Discover
Discover available tools organized by domain.
Execute
Execute a tool by name with the given parameters.
Execute graph query
Executes a Wiz Security Graph query using a structured GraphEntityQueryInput JSON object.
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 Wiz 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
