Get the profile of the authenticated Strava athlete
AI agents call get_athlete 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 athlete profile information from the Strava API. The action is read-only—it fetches existing data without creating, modifying, deleting, or executing operations. The data retrieved is limited to the authenticated user's own profile. Severity is low because misuse would only expose personal fitness profile information without enabling unauthorized actions or data modification.
From the tool's definition Tool name 'get_athlete' and description 'Get the profile of the authenticated Strava athlete' indicate a retrieval operation that queries profile data with no modification or side effects.
Attacks that exploit this kind of access
Get the profile of the authenticated Strava athlete. 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: 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 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 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. 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 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 →