Fitbit sleep logs (v1.2) across a date range. Good for week-over-week comparisons. Cached 1h.
AI agents call get_sleep_range to retrieve information from Fitbit Googlehealth without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves sleep data from Fitbit across a specified date range for analysis and comparison. It performs a read-only operation with no side effects, data modification, or destructive capability. The caching note reinforces passive data retrieval.
From the tool's definition Tool name 'get_sleep_range' and description 'Fitbit sleep logs (v1.2) across a date range' indicate retrieval of historical sleep data without modification or deletion. No action verbs like 'set', 'delete', 'log', or 'execute' are present.
Attacks that exploit this kind of access
Fitbit sleep logs (v1.2) across a date range. Good for week-over-week comparisons. Cached 1h. It is categorised as a Read tool in the Fitbit Googlehealth MCP Server, which means it retrieves data without modifying state.
Register the Fitbit Googlehealth MCP server in PolicyLayer and add a rule for get_sleep_range: 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 Fitbit Googlehealth. Nothing to install.
get_sleep_range 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_sleep_range 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_sleep_range. 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_sleep_range is provided by the Fitbit Googlehealth MCP server (tachibanayu24/fitbit-googlehealth-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 →