AI agents call heart_rate_zones to retrieve information from TinyFn without modifying anything — 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 (optional) |
Parameters from the server's own tool schema.
Even though heart_rate_zones only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Calculate heart rate training zones. It is categorised as a Read tool in the TinyFn 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 TinyFn 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 TinyFn. 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 TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
heart_rate_zones is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →