Get monthly running summary with total distance, runs, avg pace,
AI agents call get_monthly_running_summary to retrieve information from Garmin Connect MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical summary data about running performance (distance, run count, pace) with no side effects, no code execution, and no data modification. It is a straightforward read operation on user fitness metrics, consistent with other sibling tools like get_activities_by_date and get_daily_wellness.
From the tool's definition Tool name and description indicate retrieval only: 'Get monthly running summary with total distance, runs, avg pace' — fetches aggregated metrics without modifying or executing anything.
Attacks that exploit this kind of access
Get monthly running summary with total distance, runs, avg pace,. It is categorised as a Read tool in the Garmin Connect MCP MCP Server, which means it retrieves data without modifying state.
Register the Garmin Connect MCP server in PolicyLayer and add a rule for get_monthly_running_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 MCP. Nothing to install.
get_monthly_running_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_monthly_running_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_monthly_running_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_monthly_running_summary is provided by the Garmin Connect MCP server (leewnsdud/garmin-connect-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 →