heart_rate_zones
Heart-Rate Training Zones — Max heart rate and the five training zones (recovery to VO2max) from age; uses the Karvonen reserve method when a resting heart rate is given.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/heart-rate-zones.md
What heart_rate_zones does on Gateway
AI agents call heart_rate_zones to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
age | integer | Yes | Age in years |
resting_hr | integer | — | Resting heart rate in bpm (optional, enables Karvonen method) |
Parameters from the server's own tool schema.
Why heart_rate_zones is rated Low
This is a pure calculation/query tool that retrieves derived health metrics based on input. No side effects, no state changes, no external triggers. Classified as Read per the definition: 'retrieves or queries data; no side effects.'
From the tool's definition Tool computes heart-rate training zones from input parameters (age, optional resting heart rate) using the Karvonen reserve method. Returns calculated zones; no data modification, deletion, or external system effects.
Attacks that exploit this kind of access
The rule that runs heart_rate_zones safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For heart_rate_zones, this is the rule to start with:
heart_rate_zones is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every heart_rate_zones call is checked against it from then on.
Questions about heart_rate_zones
Heart-Rate Training Zones — Max heart rate and the five training zones (recovery to VO2max) from age; uses the Karvonen reserve method when a resting heart rate is given. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
heart_rate_zones accepts 2 parameters: age, resting_hr. Required: age. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for 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 Gateway. Nothing to install.
heart_rate_zones 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 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.
Set action: deny in the PolicyLayer policy for 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.
heart_rate_zones is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue