Fetches the most recent activities for the authenticated athlete.
AI agents call get-recent-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 historical activity data from the user's Strava account. It is a straightforward data retrieval function that does not modify, delete, execute code, or commit financial transactions. The blast radius of misuse is minimal—an agent could only read the user's activity history, which is already known to the account holder.
From the tool's definition Tool description states it 'Fetches the most recent activities' - a retrieval operation with no side effects. No create, modify, delete, or execute operations are described.
Attacks that exploit this kind of access
Fetches the most recent activities for the authenticated 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-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 Strava MCP Server. Nothing to install.
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 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 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.
get-recent-activities is provided by the Strava MCP Server MCP server (samitugal/strava-mcp). 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 →