Skip to main content
Book a demo

Connect Scanner to Windsurf

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

Book a demo Windsurf setup guide

Set up

Add Scanner to Windsurf in four steps

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

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

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

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

Tools

3 Scanner tools in Windsurf

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

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

  • Gateway policy (available)

    Every Scanner call from Windsurf passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

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

  • Block output after it runs (not available)

    Windsurf 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)

    Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.

In Windsurf

  • Enforcement needs Windsurf 1.12.31 or newer.
  • When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.

Frequently asked questions

Connect more

Find another combination