Get heart-related metrics for a user on a specific date.
AI agents call get_heart_metrics to retrieve information from Ultrahuman MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves health metrics (heart rate data) from the Ultrahuman platform without modifying, deleting, or executing any operations. It is purely informational, similar to sibling tools like 'get_glucose_metrics', 'get_sleep_data', and 'get_movement_data'.
From the tool's definition Tool name 'get_heart_metrics' and description 'Get heart-related metrics for a user on a specific date' indicate data retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get heart-related metrics for a user on a specific date. It is categorised as a Read tool in the Ultrahuman MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ultrahuman MCP Server MCP server in PolicyLayer and add a rule for get_heart_metrics: 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 Ultrahuman MCP Server. Nothing to install.
get_heart_metrics 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 get_heart_metrics 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 get_heart_metrics. 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.
get_heart_metrics is provided by the Ultrahuman MCP Server MCP server (vodolazkyi/ultrahuman-mcp-server). 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 →