Connect Box to Goose
Give Goose governed access to Box’s 35 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Box to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Box in Runlayer
Add Box 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 Box’s 35 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Box
Each user signs in to Box with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Box from Goose
Box’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
35 Box tools in Goose
Runlayer policy decides which of these Goose users can call. 11 read data only.
Add items to hub
Adds files, folders, or web links to a specific hub, enabling content organization within collaborative workspaces.
Copy file
Copies an existing file to a destination folder in Box (see Box API Copy file).
Copy folder
Copies an existing folder to a destination parent folder in Box (see Box API Copy folder).
Copy hub
Creates a copy of an existing Box Hub via the Hubs v3 API (POST /v3/hubs/{id}:copy).
Create file comment
Creates a new comment on a specific file.
Create folder
Creates new folders in Box.
Create hub
Creates new collaborative hubs for organizing content around specific topics, projects, or teams.
Create metadata template
Creates a new enterprise metadata template.
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 Box 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