// SCAN REPORT

Tableau MCP Server

30 tools. 6 can modify or destroy data without limits.

5 destructive tools with no built-in limits. Policy required.

Last updated: 26 Jun 2026

6 can modify or destroy data

24 read-only

30 tools total

Community server · catalogue entry verified 26/06/2026

How to control Tableau MCP Server ↓

TOOL MAP

What Tableau MCP Server exposes to your agents

Read (24) Write / Execute (1) Destructive / Financial (5)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Tableau MCP Server tools

Destructive · High delete-datasource This tool irreversibly removes data sources from Tableau, which cannot be undone. Destructive · High delete-extract-refresh-task Although the underlying datasource or workbook is not deleted, the permanent removal of a scheduled refresh task is a destructive action that irreversibly eliminates infrastructure (the refresh schedule itself). Destructive · High delete-workbook This tool irreversibly removes a workbook and its associated content from Tableau Cloud. Destructive · Medium reset-consent Resetting OAuth consent is an irreversible action on the current session's authorization state — the previously granted consent is permanently removed and cannot be undone.

6 of Tableau MCP Server's 30 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Tableau MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Tableau MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete-datasource": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "update-cloud-extract-refresh-task": {
    "limits": [
      {
        "counter": "update-cloud-extract-refresh-task_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get-datasource-metadata": {
    "limits": [
      {
        "counter": "get-datasource-metadata_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Tableau MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TABLEAU →

Instant setup, no code required.

FULL CATALOGUE

All 30 Tableau MCP Server tools

DESTRUCTIVE 5 tools

Destructive delete-datasource Permanently deletes a published data source from the current Tableau site. Restricted to Tableau site administ Destructive delete-extract-refresh-task Deletes an extract refresh task from the Tableau site. This permanently removes the scheduled extract refresh Destructive delete-workbook Permanently deletes a workbook from the current Tableau Cloud site. Restricted to Tableau site administrators Destructive revoke-access-token Revokes the access token used to authenticate the current session. After revocation the session is invalidate

WRITE 1 tools

Write update-cloud-extract-refresh-task Updates the schedule of an extract refresh task on Tableau Cloud. Use this to change how often an extract refr

READ 24 tools

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Tableau MCP Server

Can an AI agent delete data through the Tableau MCP Server MCP server? +

Yes. The Tableau MCP Server server exposes 5 destructive tools including delete-datasource, delete-extract-refresh-task, delete-workbook. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Tableau MCP Server? +

The Tableau MCP Server server has 1 write tools including update-cloud-extract-refresh-task. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Tableau MCP Server.

How many tools does the Tableau MCP Server MCP server expose? +

30 tools across 3 categories: Destructive, Read, Write. 24 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Tableau MCP Server? +

Register the Tableau MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Tableau MCP Server tool call.

Deterministic rules across all 30 Tableau MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TABLEAU →

Instant setup, no code required.

30 Tableau MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.