health_heart_rate
Get average resting heart rate over the last 7 days (bpm) from HealthKit.
This record as markdown: /tools/heznpc-airmcp/health-heart-rate.md
What health_heart_rate does on AirMCP
AI agents call health_heart_rate to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why health_heart_rate is rated Low
This tool retrieves historical health data (heart rate metrics) from HealthKit without modifying, deleting, or executing external operations. It is a pure read operation that returns aggregated personal health information. While the data is sensitive (personal health data), the tool itself has no blast radius for side effects—misuse would be an information disclosure risk rather than an operational one.
From the tool's definition Tool name 'health_heart_rate' and description 'Get average resting heart rate over the last 7 days (bpm) from HealthKit' indicate a retrieval operation with no modification or destructive capability.
Attacks that exploit this kind of access
The rule that runs health_heart_rate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health_heart_rate, this is the rule to start with:
health_heart_rate 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 AirMCP, apply this rule, and every health_heart_rate call is checked against it from then on.
Questions about health_heart_rate
Get average resting heart rate over the last 7 days (bpm) from HealthKit. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for health_heart_rate: 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 AirMCP. Nothing to install.
health_heart_rate 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 health_heart_rate 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 health_heart_rate. 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.
health_heart_rate is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue