Skip to main content
Book a demo

Connect Scanner to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Scanner 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

    Approve Scanner in Runlayer

    Add Scanner from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Cline CLI to Runlayer

    Install the Runlayer CLI so Cline CLI can reach Scanner, which runs on the user’s machine.

    Cline CLI setup guide
  3. 3

    Sign in to Scanner

    An admin adds Scanner credentials to Runlayer once. They never sit in the client’s configuration.

  4. 4

    Use Scanner from Cline CLI

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

Tools

3 Scanner tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call. 3 read data only.

  • Get Scanner context

    Get context about available Scanner indexes and data sources for investigation

  • Execute query

    Execute a search query against Scanner security data lake indexes

  • Fetch query results

    Fetch results from a previously executed Scanner query

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 Scanner 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