Get user info from Strava
AI agents call getLoggedInAthlete 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 is a straightforward read operation that retrieves authenticated user information from Strava. It has no side effects, does not modify or delete data, does not execute code, and does not involve financial transactions. The blast radius is minimal—exposure would leak user profile data but not enable destructive actions.
From the tool's definition Tool name 'getLoggedInAthlete' and description 'Get user info from Strava' indicate a retrieval operation that queries user profile information without modifying data.
Documented attack patterns abuse exactly the kind of access getLoggedInAthlete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Strava, and nothing reaches the server without passing your rules. This is the rule we recommend for getLoggedInAthlete:
{
"version": "1",
"default": "deny",
"tools": {
"getLoggedInAthlete": {}
}
}getLoggedInAthlete is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get user info from Strava. 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 getLoggedInAthlete: 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.
getLoggedInAthlete 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 getLoggedInAthlete 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 getLoggedInAthlete. 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.
getLoggedInAthlete is provided by the Strava MCP server (kw510/strava-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Strava, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 Strava tools catalogued and risk-classified — across an index of 43,000+ MCP servers.