List recent activities posted by members of a specific club.
AI agents call get_club_activities 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 queries and retrieves activity data from a Strava club without modifying, deleting, or executing any operations. It is a simple read operation that returns publicly or club-member-shared fitness data. The blast radius is minimal: the worst outcome is unauthorized access to fitness activity information that may already be visible to club members.
From the tool's definition Tool name contains 'get_' prefix and description states 'List recent activities' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List recent activities posted by members of a specific club. 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_club_activities: 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_club_activities 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_club_activities 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_club_activities. 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_club_activities is provided by the Strava MCP Server MCP server (manojanasuri16/strava-mcp-server). 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 →