Analyze time spent in each HR zone (last 4 weeks) with training balance advice
AI agents call get_hr_zone_distribution to retrieve information from Strava Training MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes historical training metrics (heart rate zone distribution) from Strava without creating, modifying, deleting, or executing any operations. It provides insights based on existing data, making it a straightforward Read category tool with minimal security risk.
From the tool's definition Tool name 'get_hr_zone_distribution' and description 'Analyze time spent in each HR zone (last 4 weeks) with training balance advice' indicate data retrieval and analysis only.
Attacks that exploit this kind of access
Analyze time spent in each HR zone (last 4 weeks) with training balance advice. It is categorised as a Read tool in the Strava Training MCP MCP Server, which means it retrieves data without modifying state.
Register the Strava Training MCP server in PolicyLayer and add a rule for get_hr_zone_distribution: 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 Strava Training MCP. Nothing to install.
get_hr_zone_distribution 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_hr_zone_distribution 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_hr_zone_distribution. 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_hr_zone_distribution is provided by the Strava Training MCP server (ArjanLig/strava-mcp). 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 →