Connect Tableau to Claude
Give Claude governed access to Tableau’s 26 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Tableau to Claude in four steps
Admins approve the server once. Everyone in Claude 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 Claude to Runlayer
Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Tableau’s 26 tools show up in Claude’s own tool list.
Claude 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 Claude
Tableau’s approved tools appear in Claude. Every call is checked against policy and recorded.
Tools
26 Tableau tools in Claude
Runlayer policy decides which of these Claude 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 Claude
Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.
Gateway policy (available)
Every Tableau call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
Compliance API import (available)
Anthropic Compliance API imports Claude web and desktop chats for review.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Stop a call before it runs (available)
Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.
Frequently asked questions
Connect more