get_continuous_heart_rate

Get continuous heart rate data recorded throughout the day. Returns 5-minute interval heart rate samples. Requires heart rate tracking to be enabled on the Polar device.

Server Polar MCP Server nelsonnew/polar-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_continuous_heart_rate does on Polar MCP Server

AI agents call get_continuous_heart_rate to retrieve information from Polar MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_continuous_heart_rate needs a policy

This tool performs a data retrieval operation only. It queries historical heart rate measurements from a Polar fitness device and returns them without any side effects, modifications, or state changes. The data is read-only access to the user's own fitness metrics.

From the tool's definition Tool retrieves ('get_') continuous heart rate data as samples at 5-minute intervals with no modification, deletion, or execution capability described.

Questions about get_continuous_heart_rate

What does the get_continuous_heart_rate tool do? +

Get continuous heart rate data recorded throughout the day. Returns 5-minute interval heart rate samples. Requires heart rate tracking to be enabled on the Polar device. It is categorised as a Read tool in the Polar MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_continuous_heart_rate? +

Register the Polar MCP Server MCP server in PolicyLayer and add a rule for get_continuous_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 Polar MCP Server. Nothing to install.

What risk level is get_continuous_heart_rate? +

get_continuous_heart_rate is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_continuous_heart_rate? +

Yes. Add a rate_limit block to the get_continuous_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.

How do I block get_continuous_heart_rate completely? +

Set action: deny in the PolicyLayer policy for get_continuous_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.

What MCP server provides get_continuous_heart_rate? +

get_continuous_heart_rate is provided by the Polar MCP Server MCP server (nelsonnew/polar-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.