Skip to main content
Book a demo

Connect Spacelift to Goose

Give Goose governed access to Spacelift’s 7 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Goose setup guide

Set up

Add Spacelift to Goose in four steps

Admins approve the server once. Everyone in Goose then gets it through the same governed connection.

  1. 1

    Add Spacelift to Runlayer

    Spacelift isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Goose to Runlayer

    Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Spacelift’s 7 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Goose setup guide
  3. 3

    Sign in to Spacelift

    Sign in the way Spacelift requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Spacelift from Goose

    Spacelift’s approved tools appear in Goose. Every call is checked against policy and recorded.

Tools

7 Spacelift tools in Goose

Runlayer policy decides which of these Goose users can call.

  • Discover

    Browse the Spacelift API schema.

  • Intent

    Manage infrastructure resources through their lifecycle.

  • Mutate

    Execute a Spacelift mutation.

  • Policy input schema

    Return a policy type's input structure, expected rule outputs and description.

  • Policy simulate

    Evaluate a draft policy body and return the decision.

  • Provider

    Discover infrastructure providers and inspect their resource/data source schemas.

  • Query

    Execute a read-only Spacelift query.

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 Spacelift 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

Find another combination