get_cardio_load_range

Get cardio load data for a date range. Returns training load metrics for each day in the specified period.

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

What get_cardio_load_range does on Polar MCP Server

AI agents call get_cardio_load_range 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_cardio_load_range needs a policy

This tool retrieves historical training load metrics within a specified date range. It performs a read-only query operation on fitness data with no side effects—no data is created, modified, deleted, or executed. The action is informational only, consistent with the broader server's purpose of accessing and analyzing Polar fitness data.

From the tool's definition Tool name 'get_cardio_load_range' and description 'Get cardio load data for a date range. Returns training load metrics' indicate pure data retrieval with no modification, deletion, or execution capabilities.

Questions about get_cardio_load_range

What does the get_cardio_load_range tool do? +

Get cardio load data for a date range. Returns training load metrics for each day in the specified period. 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_cardio_load_range? +

Register the Polar MCP Server MCP server in PolicyLayer and add a rule for get_cardio_load_range: 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_cardio_load_range? +

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

Can I rate-limit get_cardio_load_range? +

Yes. Add a rate_limit block to the get_cardio_load_range 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_cardio_load_range completely? +

Set action: deny in the PolicyLayer policy for get_cardio_load_range. 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_cardio_load_range? +

get_cardio_load_range 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.