Get heart rate and power zone distribution for a specific activity
AI agents call get_activity_zones to retrieve information from Strava 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 and queries existing fitness performance metrics (heart rate and power zone data) from a specific activity. It has no side effects, does not modify data, does not execute code, and does not delete or move money. The blast radius of misuse is minimal—an attacker could only access training data already visible to the authenticated user. Classification as Read is appropriate.
From the tool's definition Tool name 'get_activity_zones' and description 'Get heart rate and power zone distribution for a specific activity' indicates data retrieval only.
Attacks that exploit this kind of access
Get heart rate and power zone distribution for a specific activity. It is categorised as a Read tool in the Strava MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Strava MCP Server MCP server in PolicyLayer and add a rule for get_activity_zones: 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 MCP Server. Nothing to install.
get_activity_zones 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_activity_zones 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_activity_zones. 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_activity_zones is provided by the Strava MCP Server MCP server (kerkhofme/stravamcp). 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 →