# Boreon™ · Tableau Governance and Site Operations

URL: https://boreon.com/mcp/tableau-governance
Language: en

> Scan every Tableau Server or Tableau Cloud workbook for PII, PHI, leaked credentials and stale content, with TSM status and failed jobs explained.

---
Boreon MCP Layer · Tableau Server & Cloud

# Govern every workbook in one question.

The Boreon MCP Layer scans your Tableau Server or Tableau Cloud site through Tableau's own APIs, read-only, and tells you what it found in natural language.

[Book a demo](https://boreon.com/contact) [Ask Tableau Anything](https://boreon.com/mcp/tableau)

## What the scan finds.

It downloads every workbook and data source definition, not just what the Catalog indexes, so formulas and custom SQL are covered too.

- ### PII and PHI
  Every workbook and data source, calculated fields and custom SQL included.
- ### Leaked credentials
  Passwords and keys left in connections or formulas.
- ### Stale and unused
  Content nobody opens, and users who never sign in.
- ### Over-shared
  Over-permissioned content, and duplicate or orphaned data sources.

Governance scan

Scan the whole site for PII, PHI and leaked credentials.

1. Sales Pipeline Review Clean
2. Patient Intake PHI in 2 fields
3. Finance Close Password in a connection
4. Q3 Forecast (copy) Not opened in 212 days
5. Regional Ops Shared with All Users

Done. Four findings, each explained in natural language.

Illustration with sample workbooks

## Alongside the scan.

- Stale content
- Unused content
- Heaviest content
- Inactive users
- Refresh health
- Duplicate data sources
- Orphaned data sources
- External connections
- Over-permissioned content

## Run Tableau without the guesswork.

For the Tableau admin: it reads what the consoles would show you and explains it in natural language.

Tableau Server · 3 nodes

| TSM | Gateway | VizQL Server | Back­grounder | Data Server |
| --- | --- | --- | --- | --- |
| Node 1 | Running | Running | Running | Running |
| Node 2 | Running | Running | Degraded | Running |
| Node 3 | Running | Running | Running | Running |

Why did last night's extract refresh fail?

The Sales extract hit the backgrounder timeout at 02:14. It has grown past the limit, and splitting it by region would fix it.

Illustration. Tableau Cloud never touches TSM.

- ### TSM, read for you
  Process status on every node and the errors that matter, on Tableau Server.
- ### Failed jobs, explained
  Extract refreshes and subscriptions, in natural language.
- ### 3,000 help pages
  How-to answers grounded in the official Tableau docs.
- ### Six languages
  English, Japanese, German, French, Italian and Russian.

[Previous Ask Tableau Anything Tableau Server & Cloud](https://boreon.com/mcp/tableau) [Next Your LLM, Your Rules Tableau Server & Cloud](https://boreon.com/mcp/tableau-llm)

## Ask your own Tableau, live.

Bring one question from your Tableau Server or Tableau Cloud site. The Boreon MCP Layer will answer it in line, on the model you choose, and that question becomes the first thing we set up.

[Book a demo](https://boreon.com/contact) [See it live at ai.boreon.com](https://ai.boreon.com/)