Skip to main content
Book a demo

Connect Exa Websets to VS Code

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

Book a demo VS Code setup guide

Set up

Add Exa Websets 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 Exa Websets in Runlayer

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

  2. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Exa Websets’s 23 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 3

    Sign in to Exa Websets

    Sign in the way Exa Websets requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Exa Websets from VS Code

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

Tools

23 Exa Websets tools in VS Code

Runlayer policy decides which of these VS Code users can call.

  • Cancel enrichment

    Cancel a running enrichment operation.

  • Cancel search

    Cancel a running search operation.

  • Create enrichment

    Create a new enrichment for a webset.

  • Create import

    Create a new import to upload your own data (CSV) into Websets.

  • Create search

    Create a new search to find and add items to a webset.

  • Create webhook

    Create a webhook to receive real-time HTTP callbacks when events occur in your websets.

  • Create webset

    Create a new Webset collection.

  • Delete webhook

    Delete a webhook.

See all 23 Exa Websets tools

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 Exa Websets 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