Connect Wiz to VS Code
Give VS Code governed access to Wiz’s 238 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Wiz to VS Code in four steps
Admins approve the server once. Everyone in VS Code 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 VS Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Wiz’s 238 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code 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 VS Code
Wiz’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
238 Wiz tools in VS Code
Runlayer policy decides which of these VS Code 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 VS Code
Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.
Gateway policy (available)
Every Wiz call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, VS Code 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 before VS Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before VS Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.
Frequently asked questions
Connect more
