Get lifetime and recent statistics for the authenticated athlete (total runs, rides, swims, distances, etc.)
AI agents call get_athlete_stats 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 aggregate performance data (total runs, rides, swims, distances) for the authenticated user without creating, modifying, deleting, or executing anything. It has no side effects and presents minimal risk even if called inappropriately by an AI agent—it can only expose the user's own fitness statistics to themselves.
From the tool's definition Tool name 'get_athlete_stats' and description 'Get lifetime and recent statistics for the authenticated athlete' indicate a retrieval operation.
Attacks that exploit this kind of access
Get lifetime and recent statistics for the authenticated athlete (total runs, rides, swims, distances, etc.). 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_athlete_stats: 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_athlete_stats 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_athlete_stats 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_athlete_stats. 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_athlete_stats 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 →