Skip to main content
Book a demo

Connect Tableau to Cursor

Give Cursor governed access to Tableau’s 26 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cursor setup guide

Set up

Add Tableau to Cursor in four steps

Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.

  1. 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. 2

    Connect Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Tableau’s 26 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 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. 4

    Use Tableau from Cursor

    Tableau’s approved tools appear in Cursor. Every call is checked against policy and recorded.

Tools

26 Tableau tools in Cursor

Runlayer policy decides which of these Cursor 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.

See all 26 Tableau tools

Control

What Runlayer can see and stop in Cursor

Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.

  • Gateway policy (available)

    Every Tableau call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor 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 Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination