Connect Tableau to Goose
Give Goose governed access to Tableau’s 26 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Tableau to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Add Tableau to Runlayer
Tableau isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Tableau’s 26 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Tableau
Sign in the way Tableau requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Tableau from Goose
Tableau’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
26 Tableau tools in Goose
Runlayer policy decides which of these Goose users can call.
Download workbook
Downloads workbook content as a TWB (application/xml) or TWBX (application/octet-stream) file.
Generate pulse insight brief
Generate a concise insight brief for Pulse Metrics using Tableau REST API.
Generate pulse metric value insight bundle
Generate an insight bundle for the current aggregated value for Pulse Metric using Tableau REST API.
Get custom view data
Retrieves comma-separated value (CSV) data for a Tableau Custom View (saved/personalized view state), including the user's filters.
Get custom view image
Retrieves an image of the specified custom view in a published viz.
Get datasource metadata
Retrieves metadata for a specified datasource by taking the basic, high level, metadata results from Tableau's VizQL Data Service and enriches them with additional context provided by Tableau's…
Get view
Retrieves information about the specified view, including upstream datasources, workbook information, project details, owner, tags, and usage statistics.
Get view data
Retrieves data for the specified view in a Tableau workbook, including the user's filters.
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 Tableau 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