Get detailed sleep data including sleep performance score, contributors (hours vs needed, consistency, efficiency, sleep stress), and insights for a specific date
AI agents call whoop_get_sleep 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 personal health data (sleep performance scores, sleep duration, consistency metrics) from the WHOOP service. It performs a read-only query operation with no side effects on data or external systems. While the data is personal/sensitive (health information), the tool itself cannot modify, delete, or execute actions - it only fetches existing metrics.
From the tool's definition Tool name is 'whoop_get_sleep' and description states it 'Get detailed sleep data' - retrieves/queries biometric sleep metrics without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access whoop_get_sleep 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 whoop_get_sleep:
{
"version": "1",
"default": "deny",
"tools": {
"whoop_get_sleep": {}
}
}whoop_get_sleep 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 detailed sleep data including sleep performance score, contributors (hours vs needed, consistency, efficiency, sleep stress), and insights for a specific date. 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 whoop_get_sleep: 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.
whoop_get_sleep 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 whoop_get_sleep 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 whoop_get_sleep. 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.
whoop_get_sleep is provided by the Whoop MCP Server MCP server (jedpattersonn/whoop-mcp). 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.
5 Whoop MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.