Skip to main content
Book a demo

Connect LogRocket to Goose

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

Book a demo Goose setup guide

Set up

Add LogRocket to Goose in four steps

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

  1. 1

    Approve LogRocket in Runlayer

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

  2. 2

    Connect Goose to Runlayer

    Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches LogRocket’s 3 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Goose setup guide
  3. 3

    Sign in to LogRocket

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

  4. 4

    Use LogRocket from Goose

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

Tools

3 LogRocket tools in Goose

Runlayer policy decides which of these Goose users can call.

  • List organizations

    List organizations the user has access to.

  • List projects

    List projects the user has access to.

  • Use LogRocket

    Run a natural language query against LogRocket.

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