Get heart rate data
AI agents call get_heart_rates 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 existing heart rate data from Garmin Connect without creating, modifying, deleting, or executing any actions. It is a simple data query operation. The severity is low because exposure of health metrics to an AI agent poses minimal risk—the agent cannot act on this data to cause harm, and heart rate information alone cannot facilitate financial or destructive actions.
From the tool's definition Tool name 'get_heart_rates' and description 'Get heart rate data' indicate a retrieval operation with no modification or side effects. The verb 'Get' explicitly signals a read-only query.
Attacks that exploit this kind of access
Get heart rate 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_heart_rates: 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_heart_rates 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_rates 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_rates. 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_rates 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 →