Skip to main content
Book a demo

Connect Amplitude to Goose

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

Book a demo Goose setup guide

Set up

Add Amplitude to Goose in four steps

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

  1. 1

    Approve Amplitude in Runlayer

    Add Amplitude 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 Amplitude’s 49 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Goose setup guide
  3. 3

    Sign in to Amplitude

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

  4. 4

    Use Amplitude from Goose

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

Tools

49 Amplitude tools in Goose

Runlayer policy decides which of these Goose users can call.

  • Create group types

    Create one or more group types in a project, OR add already-ingested group types with status "unexpected" to the tracking plan.

  • Create properties

    Create one or more properties in a project's tracking plan.

  • Delete event properties

    Delete one or more event properties in a project.

  • Delete user properties

    Delete one or more user properties in a project.

  • Get agent results

    Retrieve results from AI agents that have analyzed your dashboards or session replays.

  • Get amp session replay info

    Unified entry point for session replay data: find replays and inspect what happened in them.

  • Get amp taxonomy

    Read a project's tracking plan: the events it defines, the properties on them, what a branch changes relative to main, who changed what when, and a CSV download of the plan.

  • Get amp user data

    Look up Amplitude users.

See all 49 Amplitude tools

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