Lists the authenticated athlete
AI agents call 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 segment effort data for the authenticated user. It queries existing Strava data without modifying, deleting, or executing external operations. The operation is read-only and has no destructive or financial consequences. Severity is low because even if misused, it only exposes the user's own fitness data already accessible through normal Strava usage.
From the tool's definition Tool name 'list-segment-efforts' and server description indicating it 'retrieves detailed activity stats' and 'segment insights'. The incomplete description 'Lists the authenticated athlete' suggests a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Lists 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 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.
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 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 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.
list-segment-efforts is provided by the Strava MCP Server MCP server (limeon-source/strava-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list-segment-efforts is one line of Strava MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →