Skip to main content
Book a demo

Connect Vimeo to Goose

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

Book a demo Goose setup guide

Set up

Add Vimeo to Goose in four steps

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

  1. 1

    Approve Vimeo in Runlayer

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

    Goose setup guide
  3. 3

    Sign in to Vimeo

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

  4. 4

    Use Vimeo from Goose

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

Tools

33 Vimeo tools in Goose

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

  • Create editing session

    Create a new editing session, returning the session ID and storyboard ID.

  • Set single text

    Set text on the visual layer with specified timing.

  • Set all texts

    Set multiple texts on the visual layer with specified timings.

  • Set media

    Add media (image, video, or sound) to the appropriate layer based on file extension.

  • Save

    Save the current editing session.

  • Render

    Render the storyboard to a video file.

  • Check render progress

    Check the progress of the current storyboard render.

  • Search

    Search your organizational content library for any recorded material including all-hands meetings, presentations, tech talks, demos, tutorials, team communications, or company content.

See all 33 Vimeo 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 Vimeo 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