Connect Socket to Goose
Give Goose governed access to Socket’s 1 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Socket to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Socket in Runlayer
Add Socket from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Goose to Runlayer
Install the Runlayer CLI so Goose can reach Socket, which runs on the user’s machine. Auto Sync can then write Socket into Goose on macOS, Windows, and Linux.
Goose setup guide - 3
Sign in to Socket
An admin adds Socket credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Socket from Goose
Socket’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
1 Socket tools in Goose
Runlayer policy decides which of these Goose users can call. 1 read data only.
Depscore
Query dependency security scores across npm, PyPI, cargo, and other package ecosystems.
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 Socket 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