Get workout history with strain, heart rate zones, duration, and calories from Whoop.
AI agents call get_workout_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 retrieves historical workout data and associated metrics without creating, modifying, deleting, or executing anything. It is a straightforward data query operation with no side effects. The low severity reflects minimal risk even if an AI agent calls it repeatedly or with manipulated parameters—it only returns existing health metrics stored in the Whoop service.
From the tool's definition Tool name 'get_workout_history' and description 'Get workout history' indicates retrieval of existing data.
Attacks that exploit this kind of access
Get workout history with strain, heart rate zones, duration, and calories 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_workout_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_workout_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_workout_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_workout_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_workout_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 →