Connect Lattice to Goose
Give Goose governed access to Lattice’s 22 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Lattice to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Lattice in Runlayer
Add Lattice 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 Lattice’s 22 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Lattice
Each user signs in to Lattice with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Lattice from Goose
Lattice’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
22 Lattice tools in Goose
Runlayer policy decides which of these Goose users can call. 15 read data only.
Find ancestors
Find ancestors.
Find employees
Searches for employees in the user's company by name, work email, and/or department.
Find feedback
Retrieves feedback items the user has visibility into.
Find one on ones
Find one on ones.
Find reports
Find reports.
Find reviews
Retrieves reviews the user is permitted to see, filterable by who the review is about, who wrote it, the cycle, direction, submission/sharing status, and date range.
Get current update draft
Returns the user's current-period update draft, with the questions on the form, any answers already saved, the period bounds, and the cadence.
Get draft reviews
Retrieves the open performance review drafts the user is currently authoring.
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 Lattice 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