Get historical cardio load data aggregated by days or months. Useful for long-term training load analysis.
AI agents call get_cardio_load_history 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.
This is a straightforward read operation that retrieves historical fitness metrics from the Polar API. It queries pre-existing aggregated cardio load data without creating, modifying, or deleting any information. The read-only nature and non-sensitive fitness data context result in low severity risk.
From the tool's definition Tool name 'get_cardio_load_history' and description 'Get historical cardio load data aggregated by days or months' indicate pure data retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get historical cardio load data aggregated by days or months. Useful for long-term training load analysis. It is categorised as a Read tool in the Polar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Polar MCP Server MCP server in PolicyLayer and add a rule for get_cardio_load_history: 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.
get_cardio_load_history 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_cardio_load_history 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_cardio_load_history. 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_cardio_load_history 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.
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 →