Get training strain history and workout data.
AI agents call get_strain_history 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 strain and workout data from Whoop's health tracking system. It performs a query operation that returns existing data without creating, modifying, deleting, or executing any operations. The blast radius is minimal as misuse would only result in unauthorized data access, not irreversible changes or external operations.
From the tool's definition Tool name 'get_strain_history' and description 'Get training strain history and workout data' indicate data retrieval with no modification. The verb 'Get' and the read-only nature of accessing historical health metrics confirm no side effects occur.
Documented attack patterns abuse exactly the kind of access get_strain_history 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_strain_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_strain_history": {}
}
}get_strain_history 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 training strain history and workout data. 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_strain_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 Whoop MCP Server. Nothing to install.
get_strain_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_strain_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_strain_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_strain_history 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.