Connect Clay to Goose
Give Goose governed access to Clay’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Clay to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Clay in Runlayer
Add Clay 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 Clay’s 21 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Clay
Sign in the way Clay requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Clay from Goose
Clay’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
21 Clay tools in Goose
Runlayer policy decides which of these Goose users can call. 12 read data only and 3 can change or delete data.
Add company data points
Add data points to companies in an existing search.
Add contact data points
Add data points to contacts in an existing search.
Ask question about accounts
Ask a natural language question about one or more accounts available in Clay Audiences.
Find and enrich company
Find and enrich a single company by domain or LinkedIn URL.
Find and enrich contacts at company
Search for contacts at a company by role, title, name, or department.
Find and enrich list of contacts
Find and enrich specific named contacts at their companies.
Get credits available
Check if credits are available for the workspace.
Get current workspace
Report which Clay workspace this connection is pinned 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 Clay 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