Get the Whoop authorization URL to connect your account.
AI agents call get_auth_url to retrieve information from Whoop MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply returns an authentication URL that initiates an OAuth flow, which is a read-only operation with no side effects. The user must separately interact with that URL to authorize access. The tool itself performs no state changes, does not execute code or commands, does not delete data, and does not involve financial transactions. It is a standard Read category operation with low severity.
From the tool's definition Tool name 'get_auth_url' and description 'Get the Whoop authorization URL' indicate retrieval of a URL endpoint. No modification, deletion, execution, or financial transaction occurs—only retrieval of a public authorization endpoint.
Documented attack patterns abuse exactly the kind of access get_auth_url 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 get_auth_url:
{
"version": "1",
"default": "deny",
"tools": {
"get_auth_url": {}
}
}get_auth_url is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the Whoop authorization URL to connect your account. It is categorised as a Read tool in the Whoop MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Whoop MCP Server MCP server in PolicyLayer and add a rule for get_auth_url: 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.
get_auth_url is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_auth_url 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 get_auth_url. 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.
get_auth_url is provided by the Whoop MCP Server MCP server (yuridivonis/whoop-mcp-server). 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.
6 Whoop MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.