Get recent activities with pagination. Returns activity summaries: type, duration, distance, calories, heart rate
AI agents call get_activities 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 only queries and retrieves historical fitness data without side effects. It performs a read-only operation on the user's Garmin Connect data, analogous to a search or fetch operation. No data is created, modified, deleted, or executed. The pagination mechanism does not change this classification.
From the tool's definition Tool retrieves activity summaries including type, duration, distance, calories, and heart rate with no modification, deletion, or execution. The description indicates a query operation with 'Returns activity summaries' and 'Get recent activities'.
Documented attack patterns abuse exactly the kind of access get_activities 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_activities:
{
"version": "1",
"default": "deny",
"tools": {
"get_activities": {}
}
}get_activities 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 recent activities with pagination. Returns activity summaries: type, duration, distance, calories, heart rate. 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_activities: 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_activities 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_activities 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_activities. 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_activities 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.