AI agents call list-athlete-routes to retrieve information from Strava without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays route data belonging to the authenticated user. It performs no mutations, deletions, or external operations—only data retrieval. The scoped access (authenticated athlete's own routes) further reduces severity. This is a straightforward Read operation.
From the tool's definition Tool description states 'Lists the routes created by the authenticated athlete' with pagination. The verb 'lists' is a read-only query operation that retrieves existing data without modification or side effects.
Attacks that exploit this kind of access
Lists the routes created by the authenticated athlete, with pagination. It is categorised as a Read tool in the Strava MCP Server, which means it retrieves data without modifying state.
Register the Strava MCP server in PolicyLayer and add a rule for list-athlete-routes: 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. Nothing to install.
list-athlete-routes 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 list-athlete-routes 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 list-athlete-routes. 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.
list-athlete-routes is provided by the Strava MCP server (@r-huijts/strava-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.