List efforts on a segment, optionally filtered by date range. Returns the authenticated athlete
AI agents call strava_list_segment_efforts 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 and queries segment effort data filtered by optional date range parameters. It has no side effects—it only reads and returns performance metrics from the Strava API. No data is created, modified, deleted, or used to trigger external actions. This is a straightforward Read operation with minimal risk if misused.
From the tool's definition Tool name contains 'list' and description states 'List efforts on a segment' with optional filtering. Returns data (authenticated athlete efforts) with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
List efforts on a segment, optionally filtered by date range. Returns 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 strava_list_segment_efforts: 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.
strava_list_segment_efforts 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_list_segment_efforts 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_list_segment_efforts. 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_list_segment_efforts is provided by the Strava MCP Server MCP server (justmytwospence/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 →