Get daily heart rate data: resting HR, max HR, min HR, and time series throughout the day
AI agents call get_heart_rate 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 personal health metrics (heart rate statistics) from Garmin Connect. It performs a read-only operation with no capability to modify, delete, or execute actions. The data returned is personal fitness information that could be sensitive, but the tool itself only retrieves it without side effects.
From the tool's definition Tool name 'get_heart_rate' and description 'Get daily heart rate data: resting HR, max HR, min HR, and time series throughout the day' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_heart_rate 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_heart_rate:
{
"version": "1",
"default": "deny",
"tools": {
"get_heart_rate": {}
}
}get_heart_rate 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 daily heart rate data: resting HR, max HR, min HR, and time series throughout the day. 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_heart_rate: 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_heart_rate 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 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. 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 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.