Connect Carta to Goose
Give Goose governed access to Carta’s 18 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Carta to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Carta in Runlayer
Add Carta 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 Carta’s 18 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Carta
Sign in the way Carta requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Carta from Goose
Carta’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
18 Carta tools in Goose
Runlayer policy decides which of these Goose users can call.
Call tool
Run a Carta tool that search_tools found.
Cap table chart
Show a visual cap table summary with ownership breakdown by share class.
Discover
List available Carta commands or views across all domains.
Fetch
Execute a named Carta read command.
Get current user
Get the currently authenticated Carta user's profile.
List accounts
List all companies and organizations the current user has access to.
List contexts
Show which firms you have access to in Carta Fund Admin and which one is currently active.
List resources
List all available resources and resource templates.
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 Carta 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