Connect Profound to Goose
Give Goose governed access to Profound’s 61 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Profound to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Add Profound to Runlayer
Profound 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 Profound’s 61 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Profound
Sign in the way Profound requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Profound from Goose
Profound’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
61 Profound tools in Goose
Runlayer policy decides which of these Goose users can call.
Add knowledge base document
Add ONE new document (inline markdown text) to a knowledge base.
Archive project
Preview or archive (retire) a project — set it aside without deleting it.
Create agent definition
Create a draft agent definition — preview first, then apply on confirmation.
Create doc
Create a new document in the Profound platform from content you have written.
Create project task
Preview or add a task ("play") to a project.
Create prompts
Create one or more prompts in a category.
Get agent
Get details of an agent, including its input_schema.
Get agent definition
Read back an agent's full workflow graph so you can copy and edit it.
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 Profound 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