Get heart rate data in different time zones for an activity
AI agents call get_activity_hr_in_timezones 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 and formats existing heart rate data from a completed activity in different time zone representations. It is a read-only operation with no side effects, data modification, or external execution. The blast radius of misuse is minimal—an agent could retrieve heart rate data across time zones, which is a privacy/sensitivity concern but not operationally dangerous.
From the tool's definition Tool name contains 'get' and description states 'Get heart rate data', indicating retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
Get heart rate data in different time zones for an activity. 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_activity_hr_in_timezones: 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_activity_hr_in_timezones 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_activity_hr_in_timezones 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_activity_hr_in_timezones. 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_activity_hr_in_timezones is provided by the Garmin MCP Server MCP server (jbaker48/garmin-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 →