AI agents use whoop-refresh-token to create or update resources in WHOOP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WHOOP MCP Server environment.
This tool exchanges a refresh token for a new access token, which modifies authentication state by issuing new credentials. It's a Write operation (creates/updates auth tokens) rather than a simple Read. Misuse could allow an agent to maintain persistent unauthorized access by continuously refreshing tokens, hence medium severity.
From the tool's definition Refresh access token using refresh token
Documented attack patterns abuse exactly the kind of access whoop-refresh-token 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-refresh-token:
{
"version": "1",
"default": "deny",
"tools": {
"whoop-refresh-token": {
"limits": [
{
"counter": "whoop-refresh-token_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} whoop-refresh-token stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Refresh access token using refresh token. It is categorised as a Write tool in the WHOOP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WHOOP MCP Server MCP server in PolicyLayer and add a rule for whoop-refresh-token: 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-refresh-token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the whoop-refresh-token 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-refresh-token. 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-refresh-token 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.