Get heart rate data for a given date.
AI agents call get_heart_rates to retrieve information from Mcp Garmin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical heart rate data without creating, modifying, deleting, or executing operations. It is a straightforward read operation on personal health metrics. The low severity reflects that exposure of personal heart rate history, while privacy-sensitive, cannot cause direct financial loss, system compromise, or irreversible harm if misused by an AI agent.
From the tool's definition Tool description states 'Get heart rate data' with no modification capability. Server description explicitly specifies 'read-only access to daily health metrics'.
Attacks that exploit this kind of access
Get heart rate data for a given date. It is categorised as a Read tool in the Mcp Garmin MCP Server, which means it retrieves data without modifying state.
Register the Mcp Garmin 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 Mcp Garmin. 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 Mcp Garmin MCP server (obrien-matthew/mcp-garmin). 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 →