get_heart_rate_zones

Get personalized heart rate training zones based on max HR and lactate threshold

Server Garmin Health MCP Server willc121/garmin-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_heart_rate_zones does on Garmin Health MCP Server

AI agents call get_heart_rate_zones to retrieve information from Garmin Health MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_heart_rate_zones needs a policy

This tool queries and retrieves precomputed or calculated health metrics from Supabase without creating, modifying, deleting, or executing code. It has no side effects and poses minimal security risk. Even if returned data were sensitive, exposure is limited to the querying user's own health data, making it a straightforward Read operation.

From the tool's definition Tool name 'get_heart_rate_zones' and description 'Get personalized heart rate training zones' indicate a retrieval operation with no modification capability. Returns computed training zone data based on stored metrics (max HR, lactate threshold).

Questions about get_heart_rate_zones

What does the get_heart_rate_zones tool do? +

Get personalized heart rate training zones based on max HR and lactate threshold. It is categorised as a Read tool in the Garmin Health MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_heart_rate_zones? +

Register the Garmin Health MCP Server MCP server in PolicyLayer and add a rule for get_heart_rate_zones: 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 Health MCP Server. Nothing to install.

What risk level is get_heart_rate_zones? +

get_heart_rate_zones is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_heart_rate_zones? +

Yes. Add a rate_limit block to the get_heart_rate_zones 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.

How do I block get_heart_rate_zones completely? +

Set action: deny in the PolicyLayer policy for get_heart_rate_zones. 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.

What MCP server provides get_heart_rate_zones? +

get_heart_rate_zones is provided by the Garmin Health MCP Server MCP server (willc121/garmin-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.