Connect Harmonic to Goose
Give Goose governed access to Harmonic’s 47 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Harmonic to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Add Harmonic to Runlayer
Harmonic 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 Harmonic’s 47 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Harmonic
Sign in the way Harmonic requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Harmonic from Goose
Harmonic’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
47 Harmonic tools in Goose
Runlayer policy decides which of these Goose users can call.
Add companies to list
Add companies to an existing company list.
Add people to list
Add people to an existing people list.
Create company list
Create a new company list.
Create company list custom field
Create a custom field (column) for a company list.
Create global custom field
Create a new global custom field for companies or people.
Create list
Create an empty company, person, or investor list in the workspace's shared project.
Create list custom field
Create a custom field on any company, person, or investor list.
Create list entries
Add Harmonic companies, people, or investors to an existing list by creating list entries from their URNs.
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 Harmonic 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
