Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/tableau/tableau-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/tableau/tableau-mcp/auth)<a href="https://agentmods.dev/rules/tableau/tableau-mcp/auth"><img src="https://agentmods.dev/badge/rules/tableau/tableau-mcp/auth/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/tableau/tableau-mcp/auth"><img src="https://agentmods.dev/badge/rules/tableau/tableau-mcp/auth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00878 |
| Opus 5.5 | $0.00000 | $0.00351 |
| Sonnet 5.5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
auth scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth Standards
Three Auth Paths
1. Passthrough Auth
- Header
x-tableau-author cookieworkgroup_session_id - Validated via
RestApi.authenticatedServerMethods.getCurrentServerSession() - Optional session caching via
ExpiringMap(configurable interval) - Location:
src/server/passthroughAuthMiddleware.ts - Enabled when
config.enablePassthroughAuthis true - MCP scopes NOT enforced (no way to verify original token scopes)
2. Embedded OAuth (PKCE)
- JWE-encrypted MCP access tokens signed with server's private key
- Contains embedded Tableau access/refresh tokens
EmbeddedAccessTokenValidatorvalidates viajose- Location:
src/server/oauth/provider.ts,accessTokenValidator.ts,token.ts,authorize.ts,callback.ts
3. Tableau Cloud OAuth
- Tableau Cloud JWT Bearer tokens
TableauAccessTokenValidatorvalidates JWT claims- Location:
src/server/oauth/provider.ts,accessTokenValidator.ts
Middleware Chain Order (express.ts)
handlePingRequest
→ passthroughAuthMiddleware (if enabled)
→ oauthProvider.authMiddleware
→ validateProtocolVersion
→ createMcpServer
Auth Info Flow
req.auth
→ getTableauAuthInfo(req.auth)
→ TableauAuthInfo (discriminated union: 'X-Tableau-Auth' | 'Bearer' | 'Passthrough')
→ TableauRequestHandlerExtra.tableauAuthInfo
→ useRestApi() (handles sign-in, token setup, sign-out lifecycle)
TableauAuthInfo Type (src/server/oauth/schemas.ts)
Discriminated union on type field:
'X-Tableau-Auth'— username, server, siteId?, userId?, accessToken?, refreshToken?'Bearer'— username, server, siteId, userId?, raw (the JWT string)'Passthrough'— username, userId, server, siteId, raw (the session token)
REST API Auth Lifecycle (src/restApiInstance.ts)
useRestApi() is the single entry point for all authenticated API calls:
- Creates a fresh
RestApiinstance per call - Routes to correct auth method based on
tableauAuthInfo.typeandconfig.auth - Auth methods:
pat,direct-trust,uat,oauth - PAT/direct-trust sessions are ephemeral (signed out after use)
- OAuth/passthrough sessions are long-lived (NOT signed out)
- Accepts
jwtScopesfor direct-trust/UAT token generation
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 87 lines · 0 tokens per session scan A 8d49ceb6fc28
auth is a cursor rule published in the GitHub repository tableau/tableau-mcp (351 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 878 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
new-tool-from-docs
This rule generates tool implementations for the Razorpay MCP server based on API documentation.
logging-standards
Use the Operative Control Center logging system instead of print statements.
chrono-mcp-standards
Chrono MCP Project Standards and Guidelines.
php-client-implementation
Guidelines for implementing MCP clients in PHP.
php-server-implementation
Guidelines for implementing MCP servers in PHP.
301-framework-spring-boot
Spring Boot development guidelines.