Returns recent exercise / activity log entries (runs, walks, workouts) in reverse chronological order.
AI agents call get_exercise_list 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 exercise data without creating, modifying, or deleting any information. It is a read-only operation with minimal blast radius if misused by an AI agent, as it only exposes existing personal health records rather than enabling destructive or financial actions.
From the tool's definition Tool name 'get_exercise_list' and description states it 'Returns recent exercise / activity log entries' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Returns recent exercise / activity log entries (runs, walks, workouts) in reverse chronological order. 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_exercise_list: 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_exercise_list 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_exercise_list 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_exercise_list. 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_exercise_list 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 →