Connect AirOps to Goose
Give Goose governed access to AirOps’s 100 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add AirOps to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve AirOps in Runlayer
Add AirOps 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 AirOps’s 100 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to AirOps
Sign in the way AirOps requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use AirOps from Goose
AirOps’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
100 AirOps tools in Goose
Runlayer policy decides which of these Goose users can call.
Accept opportunity
Accept pending opportunities for a campaign and add them to the campaign action grid.
Add AEO region
Add a region (ISO alpha-2 country code) to a Brand Kit's configured AEO regions.
Add grid column
Add a new column to a grid table.
Analytics chart
Query analytics data and display it as an interactive chart.
Automated feedback report
AirOps only feedback tool.
Bulk update AEO prompt tags
Apply a single tag operation (add or remove) to a batch of AEO prompts in one Brand Kit, atomically.
Bulk update AEO prompt topics
Reassign a batch of AEO prompts to an existing topic in one Brand Kit.
Commit AEO prompt assignments
Commit the current prompt-assignment draft for a Brand Kit to live.
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 AirOps 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