Connect Grain to Goose
Give Goose governed access to Grain’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Grain to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Grain in Runlayer
Add Grain 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 Grain’s 15 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Grain
Sign in the way Grain requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Grain from Goose
Grain’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
15 Grain tools in Goose
Runlayer policy decides which of these Goose users can call. 15 read data only.
Myself
Get information about the logged-in Grain user.
List meetings
Returns a filtered list of Grain meetings you have access to, ordered by most recent.
List attended meetings
Returns a filtered list of Grain meetings you have attended, ordered by most recent.
Fetch meeting
Fetches information about a single Grain meeting by ID.
Fetch meeting notes
Fetches the AI notes payload from a single Grain meeting by ID.
Fetch meeting transcript
Fetches the transcript from a single Grain meeting by ID.
Search persons
Returns a filtered list of persons that were participants of Grain meetings you have access to.
Search companies
Returns a filtered list of companies that were participants of Grain meetings you have access to.
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 Grain 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