Get daily strain history showing cardiovascular load over time from Whoop.
AI agents call get_strain_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 health metrics (cardiovascular strain data) from the Whoop service. It performs a read-only query operation that aggregates existing fitness data for analysis and monitoring purposes. There are no side effects, data modifications, deletions, or external state changes.
From the tool's definition Tool name 'get_strain_history' and description 'Get daily strain history showing cardiovascular load over time from Whoop' indicate a retrieval operation with no side effects. The verb 'get' and context of 'history' confirm data querying without modification.
Attacks that exploit this kind of access
Get daily strain history showing cardiovascular load over time 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_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 Health 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 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 →