Get heart rate measurements over a time period
AI agents call get_heart_rate to retrieve information from Withings 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 historical heart rate data from the Withings Health API. It performs a query operation that returns existing measurements without modifying, deleting, or executing any external operations. While the data is personal health information, the tool itself only reads and returns it. Classification as Read is appropriate for query/retrieval operations with no state changes.
From the tool's definition Tool name is 'get_heart_rate' with description 'Get heart rate measurements over a time period'. The verb 'Get' and the read-only nature of retrieving historical health measurements indicate this is a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Get heart rate measurements over a time period. It is categorised as a Read tool in the Withings MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Withings MCP Server MCP server in PolicyLayer and add a rule for get_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 Withings MCP Server. Nothing to install.
get_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 get_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 get_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.
get_heart_rate is provided by the Withings MCP Server MCP server (schimmilab/withings-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 →