Get Heart Rate Variability (HRV) data
AI agents call get_hrv_data 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 existing health/fitness data from Garmin Connect without creating, modifying, deleting, or executing any operations. HRV data is historical biometric information that the tool merely retrieves. There is no blast radius from misuse—accessing HRV data poses minimal security risk compared to tools that write data or trigger external operations.
From the tool's definition Tool name 'get_hrv_data' and description 'Get Heart Rate Variability (HRV) data' indicate a retrieval operation with no modification or side effects. The verb 'get' is a clear read operation.
Attacks that exploit this kind of access
Get Heart Rate Variability (HRV) data. 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_data: 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_data 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_data 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_data. 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_data is provided by the Garmin MCP Server MCP server (shubhaankar-sharma/garmin-mcp-railway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →