mcmillan_heart_rate_zones
AI agents call mcmillan_heart_rate_zones to retrieve information from Running Formulas MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the server description mentioning 'heart rate zones' as one of the calculations provided, and the naming pattern consistent with other read-only calculation tools on this server (e.g., calculate_training_paces, predict_race_time), this tool almost certainly computes and returns heart rate zone data from user inputs. No write, execute, destructive, or financial operations are implied.
From the tool's definition Tool name 'mcmillan_heart_rate_zones' and server context describing heart rate zone calculations using Greg McMillan methodology. Description is empty.
Attacks that exploit this kind of access
mcmillan_heart_rate_zones. It is categorised as a Read tool in the Running Formulas MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Running Formulas MCP Server MCP server in PolicyLayer and add a rule for mcmillan_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 Running Formulas MCP Server. Nothing to install.
mcmillan_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 mcmillan_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 mcmillan_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.
mcmillan_heart_rate_zones is provided by the Running Formulas MCP Server MCP server (st3v/running-formulas-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 →