Skip to main content
Book a demo

Connect Nimble to Claude

Give Claude governed access to Nimble’s 27 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude setup guide

Set up

Add Nimble to Claude in four steps

Admins approve the server once. Everyone in Claude then gets it through the same governed connection.

  1. 1

    Approve Nimble in Runlayer

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

  2. 2

    Connect Claude to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Nimble’s 27 tools show up in Claude’s own tool list.

    Claude setup guide
  3. 3

    Sign in to Nimble

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

  4. 4

    Use Nimble from Claude

    Nimble’s approved tools appear in Claude. Every call is checked against policy and recorded.

Tools

27 Nimble tools in Claude

Runlayer policy decides which of these Claude users can call. 16 read data only and 5 can change or delete data.

  • Nimble crawl run

    Nimble Crawl: one-time bulk fetch of a known doc tree or URL list.

  • Nimble crawl status

    Check the status and progress of a running or completed crawl job.

  • Nimble crawl list

    List crawl jobs, optionally filtered by status.

  • Nimble crawl terminate

    Cancel a running or queued crawl job.

  • List extraction templates

    Browse Extraction Templates — reusable, site-specific structured scrapers.

  • Get extraction template

    Get an Extraction Template's input/output schema before running it.

  • Run extraction template

    Run an Extraction Template against 1–few known items (URL or site ID).

  • Generate extraction template

    Generate a new Extraction Template — only when the user explicitly asks to.

See all 27 Nimble tools

Control

What Runlayer can see and stop in Claude

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination