Get heart rate and power zone distribution for an activity. Shows time spent in each zone.
AI agents call strava_list_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 queries existing activity performance metrics and returns zone distribution information. It has no side effects, does not create, modify, or delete data, and does not execute external operations. It is purely a read operation accessing fitness analytics data already associated with the user's account.
From the tool's definition Tool retrieves and displays heart rate and power zone distribution data for an activity with no modification or deletion. Description uses passive language 'Get' and 'Shows', indicating data retrieval only.
Attacks that exploit this kind of access
Get heart rate and power zone distribution for an activity. Shows time spent in each zone. 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 strava_list_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.
strava_list_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 strava_list_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 strava_list_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.
strava_list_activity_zones is provided by the Strava MCP Server MCP server (justmytwospence/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 →