Resets saved OAuth consent for the current user on the Tableau authorization server. After resetting consent, the current session remains valid. The next OAuth authorization flow will re-prompt the user for consent. This tool requires no input — it operates on the token already associated with th...
AI agents call reset-consent to permanently remove resources in Tableau MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
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. The next OAuth flow will require the user to re-consent, disrupting any automated or delegated access that relied on the saved consent.
From the tool's definition Resets saved OAuth consent for the current user on the Tableau authorization server... The next OAuth authorization flow will re-prompt the user for consent.
Attacks that exploit this kind of access
Resets saved OAuth consent for the current user on the Tableau authorization server. After resetting consent, the current session remains valid. The next OAuth authorization flow will re-prompt the user for consent. This tool requires no input — it operates on the token already associated with the current session and never exposes the raw token value. Important: Call this tool before revoking the access token. Revocation invalidates the token required to authenticate the consent reset request. When to use: - Clearing previously granted OAuth consent as part of session teardown - Resetting consent state during testing or development - Cleaning up OAuth grants when a user. It is categorised as a Destructive tool in the Tableau MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tableau MCP Server MCP server in PolicyLayer and add a rule for reset-consent: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Tableau MCP Server. Nothing to install.
reset-consent is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reset-consent rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for reset-consent. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
reset-consent is provided by the Tableau MCP Server MCP server (tableau/tableau-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.