Connect Serval to Goose
Give Goose governed access to Serval’s 402 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Serval to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Add Serval to Runlayer
Serval isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Serval’s 402 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Serval
Sign in the way Serval requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Serval from Goose
Serval’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
402 Serval tools in Goose
Runlayer policy decides which of these Goose users can call.
Add entity type field
Deprecated: use POST /v2/entity-type-fields.
Add label to app instance
DEPRECATED: use AddTagToSubject.
Add tag to subject
Attach a tag to a subject (resource, role, app instance, workflow, or guidance).
Add ticket assignment group
Add a group to the team's configured assignment groups.
Add ticket relevant asset
Add a relevant asset to a ticket.
Aggregate entities
Aggregate live-entity counts for one entity schema (database), grouped by entity type or by creation-time bucket (day or month).
Archive entity
Archive an entity, hiding it from active browse while keeping its key reserved so the key cannot be reused.
Archive ticket
Move a ticket into cold storage, removing it from most views.
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 Serval 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