AI agents call get_average_strain 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 performs a read-only calculation on historical health metrics (strain data). It queries and aggregates data but produces no side effects, creates no new records, executes no arbitrary code, and makes no financial transactions. All sibling tools on this server (get_cycle_by_id, get_cycles, get_latest_cycle, etc.) are similarly read-only data retrieval operations, confirming the pattern.
From the tool's definition Tool name 'get_average_strain' and description 'Calculate average strain over the specified number of days' indicate a query/calculation operation that retrieves and aggregates existing strain data from the Whoop API without modifying any data.
Attacks that exploit this kind of access
Calculate average strain over the specified number of days. 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_average_strain: 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_average_strain 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_average_strain 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_average_strain. 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_average_strain is provided by the Whoop MCP server (khushishelat/ctvidic_whoop-mcp-server). 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 →