Get the Performance Management Chart (CTL/ATL/TSB) over a date range. Returns Chronic Training Load (CTL, 42-day fitness), Acute Training Load (ATL, 7-day fatigue), Training Stress Balance (TSB = CTL - ATL, form/freshness), and Acute:Chronic Workload Ratio (ACWR) per day. Use this to assess wheth...
AI agents call get_training_load_trend to retrieve information from Garmin MCP Server 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 training load analytics from Garmin Connect. It performs a read-only operation that returns computed training stress metrics. There is no ability to modify, delete, or execute external operations. The blast radius of misuse is minimal—an attacker gains visibility into an athlete's training progression but cannot alter data or trigger actions.
From the tool's definition Tool 'get_training_load_trend' retrieves performance management chart data (CTL/ATL/TSB/ACWR) over a date range with no modification capability. Returns calculated metrics derived from existing fitness data. No side effects or data alteration.
Documented attack patterns abuse exactly the kind of access get_training_load_trend gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_training_load_trend:
{
"version": "1",
"default": "deny",
"tools": {
"get_training_load_trend": {}
}
}get_training_load_trend 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 the Performance Management Chart (CTL/ATL/TSB) over a date range. Returns Chronic Training Load (CTL, 42-day fitness), Acute Training Load (ATL, 7-day fatigue), Training Stress Balance (TSB = CTL - ATL, form/freshness), and Acute:Chronic Workload Ratio (ACWR) per day. Use this to assess whether the athlete is building fitness, peaking, or accumulating too much fatigue. Recommended range: 4-8 weeks. Maximum: 90 days. Args: start_date: Start date in YYYY-MM-DD format end_date: End date in YYYY-MM-DD format. It is categorised as a Read tool in the Garmin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for get_training_load_trend: 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 MCP Server. Nothing to install.
get_training_load_trend 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_training_load_trend 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_training_load_trend. 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_training_load_trend is provided by the Garmin MCP Server MCP server (taxuspt/garmin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 126 Garmin MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
126 Garmin MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.