AI agents call get_workouts to retrieve information from Whoop 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 metrics (sport type, strain score, heart rate zones) from the Whoop fitness platform. It has no side effects—it queries existing data without creating, modifying, deleting, or executing external operations. The blast radius of misuse is minimal; an agent could retrieve workout data it shouldn't access, but cannot alter data or trigger actions.
From the tool's definition Tool name 'get_workouts' and description 'Get workout data' indicate data retrieval with no modification. Sibling tools (get_body_measurement, get_cycles, get_profile, get_recovery, get_sleep) all use 'get_' prefix pattern consistent with read-only queries.
Attacks that exploit this kind of access
Get workout data including sport type, strain score, heart rate zones,. It is categorised as a Read tool in the Whoop MCP Server, which means it retrieves data without modifying state.
Register the Whoop MCP server in PolicyLayer and add a rule for get_workouts: 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. Nothing to install.
get_workouts 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_workouts 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_workouts. 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_workouts is provided by the Whoop MCP server (saadh05/whoop-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 →