Get fitness progress stats over a date range: distance, duration, or calories grouped by activity type
AI agents call get_progress_summary to retrieve information from Garmin Connect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates historical fitness statistics over a date range without creating, modifying, deleting, or executing any operations. It is a pure query operation with no side effects on the user's data or system state. The blast radius of misuse is minimal—an agent could only over-retrieve data it is already authorized to see.
From the tool's definition Tool description states it 'Get[s] fitness progress stats' with no mention of modifications, deletions, or state changes. The verb 'Get' and the pattern of querying aggregated metrics (distance, duration, calories) aligns with read-only data retrieval.
Documented attack patterns abuse exactly the kind of access get_progress_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin Connect, and nothing reaches the server without passing your rules. This is the rule we recommend for get_progress_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_progress_summary": {}
}
}get_progress_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get fitness progress stats over a date range: distance, duration, or calories grouped by activity type. It is categorised as a Read tool in the Garmin Connect MCP Server, which means it retrieves data without modifying state.
Register the Garmin Connect MCP server in PolicyLayer and add a rule for get_progress_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 Garmin Connect. Nothing to install.
get_progress_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_progress_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_progress_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_progress_summary is provided by the Garmin Connect MCP server (nicolasvegam/garmin-connect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 97 Garmin Connect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
97 Garmin Connect tools catalogued and risk-classified — across an index of 42,500+ MCP servers.