Connect Hugeicons to Goose
Give Goose governed access to Hugeicons’s 5 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Hugeicons to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Hugeicons in Runlayer
Add Hugeicons 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 Hugeicons’s 5 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Hugeicons
Sign in the way Hugeicons requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Hugeicons from Goose
Hugeicons’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
5 Hugeicons tools in Goose
Runlayer policy decides which of these Goose users can call.
List icons
Get a list of all available Hugeicons icons
Search icons
Search for icons by name or tags.
Get platform usage
Get platform-specific usage instructions for Hugeicons
Get icon glyphs
Get all glyphs (unicode characters) for a specific icon across all available styles
Get icon glyph by style
Get the glyph (unicode character) for a specific icon with a particular style
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 Hugeicons 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