Skip to main content
Book a demo

Connect Scanner to Goose

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

Book a demo Goose setup guide

Set up

Add Scanner to Goose in four steps

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

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

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

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

Tools

3 Scanner tools in Goose

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Goose’s model sees it.

  • Redact output in place (not available)

    Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination