Connect Lever to Goose
Give Goose governed access to Lever’s 13 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Lever to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Lever in Runlayer
Add Lever 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 Lever’s 13 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Lever
Sign in the way Lever requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Lever from Goose
Lever’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
13 Lever tools in Goose
Runlayer policy decides which of these Goose users can call. 8 read data only and 1 can change or delete data.
List opportunities
List opportunities (candidates) in Lever with optional filters.
Get opportunity
Get detailed information about a specific opportunity (candidate) by ID.
Update stage
Move a candidate to a different pipeline stage.
Archive opportunity
Archive a candidate with a specific reason.
Add tags
Add tags to an opportunity (candidate).
Remove tags
Remove tags from an opportunity (candidate).
List postings
List job postings in Lever with optional filters.
Get posting
Get detailed information about a specific job posting by ID.
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 Lever 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