Skip to main content
Book a demo

Connect Scanner to VS Code

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

Book a demo VS Code setup guide

Set up

Add Scanner to VS Code in four steps

Admins approve the server once. Everyone in VS Code 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 VS Code to Runlayer

    Install the Runlayer CLI so VS Code can reach Scanner, which runs on the user’s machine. Auto Sync can then write Scanner into VS Code on macOS, Windows, and Linux.

    VS Code 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 VS Code

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

Tools

3 Scanner tools in VS Code

Runlayer policy decides which of these VS Code 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 VS Code

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

  • Gateway policy (available)

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

Find another combination