Get moderate and vigorous intensity minutes for a date
AI agents call get_intensity_minutes 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 historical fitness metrics (intensity minutes) for a specified date. It performs no side effects, does not modify or delete data, and does not execute external operations. It is a straightforward read/query operation consistent with other data retrieval tools in the Garmin Connect API (e.g., get_activities, get_activity_details).
From the tool's definition Tool name 'get_intensity_minutes' and description 'Get moderate and vigorous intensity minutes for a date' indicate data retrieval only. The verb 'Get' and absence of any modification, deletion, or execution capability confirm this is a query operation.
Documented attack patterns abuse exactly the kind of access get_intensity_minutes 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_intensity_minutes:
{
"version": "1",
"default": "deny",
"tools": {
"get_intensity_minutes": {}
}
}get_intensity_minutes 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 moderate and vigorous intensity minutes for a date. 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_intensity_minutes: 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_intensity_minutes 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_intensity_minutes 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_intensity_minutes. 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_intensity_minutes 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.