Get HRV data over a date range (day-by-day). Returns array of {date, data} records
AI agents call get_hrv_range 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 queries and retrieves Heart Rate Variability (HRV) health metrics over a specified date range, returning historical data without creating, modifying, deleting, or executing any operations. It is a pure data retrieval function with no side effects, fitting the Read category. Low severity because exposure of this data poses minimal risk to system integrity, though it may reveal personal health information.
From the tool's definition Tool name 'get_hrv_range' and description 'Get HRV data over a date range' indicate a retrieval operation with no modification or side effects. Returns read-only data records.
Documented attack patterns abuse exactly the kind of access get_hrv_range 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_hrv_range:
{
"version": "1",
"default": "deny",
"tools": {
"get_hrv_range": {}
}
}get_hrv_range 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 data over a date range (day-by-day). Returns array of {date, data} records. 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_hrv_range: 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_hrv_range 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_range 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_range. 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_range 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.