Connect DX Data Cloud to Goose
Give Goose governed access to DX Data Cloud’s 10 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add DX Data Cloud to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve DX Data Cloud in Runlayer
Add DX Data Cloud 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 DX Data Cloud’s 10 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to DX Data Cloud
An admin adds DX Data Cloud credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use DX Data Cloud from Goose
DX Data Cloud’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
10 DX Data Cloud tools in Goose
Runlayer policy decides which of these Goose users can call.
Get entity details
Get comprehensive details about a specific entity including its information, tasks, and scorecards - we can use this to check operational readiness/health of an entity.
Get initiative details
Get initiative details including both the initiative info and its progress report.
Get scorecard info
Retrieve details about a specific scorecard, including its defined levels and checks.
Get team details
Retrieve details for an individual team.
List entities
List entities from the DX software catalog.
List initiatives
Lists all initiatives with summary information.
List scorecards
List all active scorecards.
List teams
List all teams in DX.
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 DX Data Cloud 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
