strava_get_recent_activities
AI agents call strava_get_recent_activities to retrieve information from FitnessMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves activity data from Strava (a fitness tracking platform). Retrieving recent activities is a read-only operation with no side effects—it does not create, modify, delete, or execute actions. The blast radius of misuse is minimal: an AI could read a user's activity history, which is a privacy concern but not operationally damaging.
From the tool's definition Tool name 'strava_get_recent_activities' uses the verb 'get', which indicates retrieval of existing data without modification. The absence of description is noted, but the naming convention is explicit.
Attacks that exploit this kind of access
strava_get_recent_activities. It is categorised as a Read tool in the FitnessMCP MCP Server, which means it retrieves data without modifying state.
Register the Fitness MCP server in PolicyLayer and add a rule for strava_get_recent_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 FitnessMCP. Nothing to install.
strava_get_recent_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 strava_get_recent_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 strava_get_recent_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.
strava_get_recent_activities is provided by the Fitness MCP server (senoj100-alt/fitnessmcp). 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 →