Get activities within a specific date range.
AI agents call get_activities_by_date 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 fitness activity data filtered by date. It does not create, modify, delete, execute code, or initiate external operations. The worst-case misuse is unauthorized exposure of a user's historical fitness data, which is a privacy/confidentiality concern but not destructive, financial, or operationally dangerous.
From the tool's definition Tool description explicitly states 'Get activities within a specific date range' — a retrieval operation with no side effects. The verb 'Get' and the read-only nature of querying activities by date confirm this is a data retrieval action.
Attacks that exploit this kind of access
Get activities within a specific date range. 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_by_date: 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_by_date 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_by_date 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_by_date. 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_by_date 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 →