Connect Ordinal to Goose
Give Goose governed access to Ordinal’s 50 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ordinal to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Ordinal in Runlayer
Add Ordinal 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 Ordinal’s 50 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Ordinal
An admin adds Ordinal credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Ordinal from Goose
Ordinal’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
50 Ordinal tools in Goose
Runlayer policy decides which of these Goose users can call.
Get analytics cpm
Get CPM Values - Retrieve the current CPM (Cost Per Mille) values used for EMV calculations across all platforms.
Update analytics cpm
Update CPM Values - Update the CPM values used for EMV calculations.
Analytics linkedin followers
Retrieve follower count history for a LinkedIn profile.
Analytics linkedin posts
Retrieve post analytics for a LinkedIn profile within a date range.
Analytics x followers
Retrieve follower count history for an X profile.
Analytics x posts
Retrieve post analytics for an X profile within a date range.
Create approvals
Create one or more approval requests for a post.
Delete approvals
Delete an approval request.
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 Ordinal 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