Get HRV (Heart Rate Variability) trend over a date range. Returns daily HRV values and weekly rolling averages. Single-day HRV is too noisy to act on — use this tool to identify baseline shifts that signal accumulated fatigue or recovery. A drop of >10ms from the 7-day baseline warrants reducing ...
AI agents call get_hrv_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 retrieves and queries historical health metrics (HRV data) within a specified date range. It performs read-only operations on the user's personal fitness data without any side effects, modifications to data, code execution, or financial implications. The tool accepts date parameters to filter the data returned, but produces no irreversible changes.
From the tool's definition Tool name 'get_hrv_trend' and description 'Get HRV (Heart Rate Variability) trend over a date range. Returns daily HRV values and weekly rolling averages.' indicates retrieval of existing fitness data with no modification, creation, deletion, or execution of…
Documented attack patterns abuse exactly the kind of access get_hrv_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_hrv_trend:
{
"version": "1",
"default": "deny",
"tools": {
"get_hrv_trend": {}
}
}get_hrv_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 HRV (Heart Rate Variability) trend over a date range. Returns daily HRV values and weekly rolling averages. Single-day HRV is too noisy to act on — use this tool to identify baseline shifts that signal accumulated fatigue or recovery. A drop of >10ms from the 7-day baseline warrants reducing training load. Recommended range: 7-21 days. Maximum: 30 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_hrv_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_hrv_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_hrv_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_hrv_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_hrv_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.