Connect Zoom to Goose
Give Goose governed access to Zoom’s 20 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Zoom to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Zoom in Runlayer
Add Zoom from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Zoom’s 20 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Zoom
Each user signs in to Zoom with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Zoom from Goose
Zoom’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
20 Zoom tools in Goose
Runlayer policy decides which of these Goose users can call.
Ask
READ-ONLY
Canvas add file collaborators
Adds collaborators (Zoom users, Team Chat channels, or email addresses) to a Zoom Canvas (formerly Zoom Docs) file, granting them a specified access role.
Canvas list file collaborators
Retrieves the list of collaborators for a specified Zoom Canvas (formerly Zoom Docs) file (supports doc and data table file types only).
Canvas modify file collaborator role
Modifies the role of an existing collaborator on a Zoom Canvas (formerly Zoom Docs) file.
Canvas remove file collaborator
Removes a specified collaborator from a file in Zoom Canvas (formerly Zoom Docs).
Create new file with markdown
⚠️ DEPRECATED: This tool has been replaced by hub_create_file_from_content.
Get file content
[DEPRECATED] This tool is deprecated.
Get meeting assets
READ-ONLY
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 Zoom 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