Get the authenticated athlete's recent activities.
AI agents call get_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 retrieves historical activity data from Strava for the authenticated user. It performs a simple data query with no capability to modify, delete, or execute external operations. The worst-case misuse is information disclosure of the user's own activity history, which is low severity. The operation is deterministic and read-only.
From the tool's definition Tool description states 'Get the authenticated athlete's recent activities' - a query operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_activities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Strava MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_activities:
{
"version": "1",
"default": "deny",
"tools": {
"get_activities": {}
}
}get_activities 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 the authenticated athlete's recent activities. 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_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_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_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_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_activities is provided by the Strava MCP Server MCP server (tomekkorbak/strava-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Strava MCP Server, 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.
4 Strava MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.