Steps, calories out, distance, heart rate zones (resting + zone minutes), active-minute bucket totals for a single day. Cached for 1 hour. NOTE: values for the current JST day can be unstable until Fitbit finalises aggregation (e.g. negative
AI agents call get_daily_summary 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 historical health summary data from Fitbit without creating, modifying, or deleting any information. It has no side effects beyond data retrieval. The 1-hour caching and note about current-day instability confirm it is purely a read operation. Even in the context of a server with destructive sibling tools (delete_*), this specific tool only fetches data.
From the tool's definition Tool name is 'get_daily_summary' and description states it 'Steps, calories out, distance, heart rate zones...for a single day.' This retrieves aggregated health metrics without modification or side effects.
Attacks that exploit this kind of access
Steps, calories out, distance, heart rate zones (resting + zone minutes), active-minute bucket totals for a single day. Cached for 1 hour. NOTE: values for the current JST day can be unstable until Fitbit finalises aggregation (e.g. negative. 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_daily_summary: 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_daily_summary 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_daily_summary 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_daily_summary. 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_daily_summary 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 →