Get daily heart rate data including resting HR, max HR, and average HR.
AI agents call get_heart_rate_data to retrieve information from Garmin Connect MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical health metrics from the Garmin Connect platform. It performs a read-only query operation with no side effects, no data modification, and no external execution. While heart rate data is personal health information, the retrieval itself poses minimal risk when used appropriately.
From the tool's definition Tool name 'get_heart_rate_data' and description 'Get daily heart rate data including resting HR, max HR, and average HR' indicate data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get daily heart rate data including resting HR, max HR, and average HR. It is categorised as a Read tool in the Garmin Connect MCP MCP Server, which means it retrieves data without modifying state.
Register the Garmin Connect MCP server in PolicyLayer and add a rule for get_heart_rate_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 Connect MCP. Nothing to install.
get_heart_rate_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_heart_rate_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_heart_rate_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_heart_rate_data is provided by the Garmin Connect MCP server (leewnsdud/garmin-connect-mcp). 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 →