List clubs for authenticated athlete
AI agents call listAthleteClubs 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 queries and returns information about clubs associated with an authenticated user. It performs a read-only operation that retrieves data without creating, modifying, deleting, or executing any side effects. The 'list' verb and passive description confirm it is a simple data retrieval function, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'listAthleteClubs' and description 'List clubs for authenticated athlete' indicate a data retrieval operation with no modification or destructive capability.
Documented attack patterns abuse exactly the kind of access listAthleteClubs 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 listAthleteClubs:
{
"version": "1",
"default": "deny",
"tools": {
"listAthleteClubs": {}
}
}listAthleteClubs 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.
List clubs for authenticated athlete. 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 listAthleteClubs: 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.
listAthleteClubs 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 listAthleteClubs 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 listAthleteClubs. 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.
listAthleteClubs 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.