Get WHOOP physiological cycle data (daily summaries) with optional date range and limit
AI agents call get_whoop_cycles 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 WHOOP fitness and physiological data without side effects. It accepts optional parameters (date range, limit) to filter results but does not create, modify, delete, or execute operations. The worst-case misuse is unauthorized data access to personal fitness metrics, which is a confidentiality concern but not a blast radius risk like financial, destructive, or code execution operations.
From the tool's definition Tool name 'get_whoop_cycles' with description 'Get WHOOP physiological cycle data (daily summaries)' uses the retrieval verb 'Get' and explicitly retrieves data with no mention of modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access get_whoop_cycles 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_whoop_cycles:
{
"version": "1",
"default": "deny",
"tools": {
"get_whoop_cycles": {}
}
}get_whoop_cycles 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 WHOOP physiological cycle data (daily summaries) with optional date range and limit. 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_whoop_cycles: 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_whoop_cycles 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_whoop_cycles 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_whoop_cycles. 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_whoop_cycles is provided by the WHOOP MCP Server MCP server (romanevstigneev/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.
7 WHOOP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.