Skip to main content

Connect Wiz to Cline CLI

Give Cline CLI governed access to Wiz’s 238 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Wiz to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.

  1. 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. 2

    Connect Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Wiz’s 238 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI setup guide
  3. 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. 4

    Use Wiz from Cline CLI

    Wiz’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.

Tools

238 Wiz tools in Cline CLI

Runlayer policy decides which of these Cline 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.

See all 238 Wiz tools

Control

What Runlayer can see and stop in Cline CLI

Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Wiz call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline 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 before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination