Time-series heart rate for a single day at the requested resolution. 1sec is only reliable during logged exercises; 1min is best for all-day trends. Personal Fitbit apps have immediate intraday access. NOTE: Fitbit itself sometimes returns an empty or partial dataset even when heart-rate zone sum...
AI agents call get_heart_rate_intraday 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 is a pure data retrieval operation that queries historical health metrics from Fitbit. It has no side effects, does not modify or delete data, and does not execute external commands or trigger financial transactions. The tool simply returns aggregated heart rate information at different time granularities.
From the tool's definition Tool retrieves time-series heart rate data for a single day at requested resolution. Described as fetching data ('Time-series heart rate', 'intraday access') with no modification, creation, or deletion capability mentioned.
Attacks that exploit this kind of access
Time-series heart rate for a single day at the requested resolution. 1sec is only reliable during logged exercises; 1min is best for all-day trends. Personal Fitbit apps have immediate intraday access. NOTE: Fitbit itself sometimes returns an empty or partial dataset even when heart-rate zone summaries are complete — this is especially common on days with logged exercise sessions, where Fitbit appears to prune intraday points around the workout interval. The. 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_heart_rate_intraday: 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_heart_rate_intraday 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_heart_rate_intraday 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_heart_rate_intraday. 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_heart_rate_intraday 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 →