Revoke the access token granted by the user
AI agents call whoop-revoke-user-access to permanently remove resources in WHOOP MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking an access token is an irreversible action that permanently invalidates the OAuth token, cutting off all API access. This cannot be undone without going through the full OAuth authorization flow again. If misused by an AI agent, it would break all WHOOP integrations for the user, making it a high-severity destructive action.
From the tool's definition Revoke the access token granted by the user
Documented attack patterns abuse exactly the kind of access whoop-revoke-user-access gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WHOOP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for whoop-revoke-user-access:
{
"version": "1",
"default": "deny",
"hide": [
"whoop-revoke-user-access"
]
} whoop-revoke-user-access disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Revoke the access token granted by the user. It is categorised as a Destructive tool in the WHOOP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WHOOP MCP Server MCP server in PolicyLayer and add a rule for whoop-revoke-user-access: 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 WHOOP MCP Server. Nothing to install.
whoop-revoke-user-access 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 whoop-revoke-user-access 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 whoop-revoke-user-access. 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.
whoop-revoke-user-access is provided by the WHOOP MCP Server MCP server (nissand/whoop-mcp-server-claude). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WHOOP MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 WHOOP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.