Record a sleep session that was not auto-detected. Duration is in milliseconds. Useful for nap logging or catch-up after forgetting to wear the device.
AI agents use log_sleep to create or update resources in Fitbit Googlehealth — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fitbit Googlehealth environment.
This tool writes a new sleep record to the user's Fitbit account. It is a Write operation (create/log), not destructive or financial. Misuse could result in inaccurate health data, giving it medium severity.
From the tool's definition "Record a sleep session" — creates a new sleep log entry in Fitbit; described as useful for 'nap logging or catch-up after forgetting to wear the device', indicating a reversible data creation action.
Attacks that exploit this kind of access
Record a sleep session that was not auto-detected. Duration is in milliseconds. Useful for nap logging or catch-up after forgetting to wear the device. It is categorised as a Write tool in the Fitbit Googlehealth MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fitbit Googlehealth MCP server in PolicyLayer and add a rule for log_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 Fitbit Googlehealth. Nothing to install.
log_sleep is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the log_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 log_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.
log_sleep 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 →