Skip to main content
Book a demo

Connect Exa Websets to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Exa Websets 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 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 Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Exa Websets’s 23 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI 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 Cline CLI

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

Tools

23 Exa Websets tools in Cline CLI

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

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

  • Gateway policy (available)

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