Get recovery history over a date range with trends and statistics from Whoop.
AI agents call get_recovery_history to retrieve information from Health MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical recovery data with trends and statistics—a classic Read operation with no side effects. It aggregates fitness data for analysis and monitoring, which is the stated purpose of the Health MCP Server. No write, delete, execute, or financial operations are possible.
From the tool's definition Tool name 'get_recovery_history' and description 'Get recovery history over a date range with trends and statistics from Whoop' indicate data retrieval only.
Attacks that exploit this kind of access
Get recovery history over a date range with trends and statistics from Whoop. It is categorised as a Read tool in the Health MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Health MCP Server MCP server in PolicyLayer and add a rule for get_recovery_history: 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 Health MCP Server. Nothing to install.
get_recovery_history 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_history 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_history. 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_history is provided by the Health MCP Server MCP server (marholoubek/health_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →