Get recovery score trends over time, including HRV and resting heart rate patterns.
AI agents call get_recovery_trends 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 retrieves historical health metrics (recovery scores, HRV, resting heart rate) from the Whoop API without modifying data or triggering external actions. It is a straightforward query operation with no side effects. The low severity reflects minimal risk even if misused—an AI agent querying this endpoint cannot cause harm beyond potential privacy exposure of already-authorized user health data.
From the tool's definition Tool name 'get_recovery_trends' and description 'Get recovery score trends over time' indicate data retrieval with no modification. The verb 'get' and absence of any write, delete, or execute operations confirm read-only functionality.
Documented attack patterns abuse exactly the kind of access get_recovery_trends 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_recovery_trends:
{
"version": "1",
"default": "deny",
"tools": {
"get_recovery_trends": {}
}
}get_recovery_trends 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 recovery score trends over time, including HRV and resting heart rate patterns. 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_recovery_trends: 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_recovery_trends 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_recovery_trends 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_recovery_trends. 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_recovery_trends 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.