AI agents call list-segment-efforts to retrieve information from Strava 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 segment effort information associated with the authenticated athlete. It performs a data retrieval operation with no side effects, no data modification, and no external code execution. The blast radius is minimal as it only returns existing data about the user's activities on segments.
From the tool's definition Tool name 'list-segment-efforts' and description 'Lists the authenticated athlete' indicate retrieval of segment effort data for the current authenticated user. The verb 'lists' confirms read-only data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Lists the authenticated athlete. It is categorised as a Read tool in the Strava MCP Server, which means it retrieves data without modifying state.
Register the Strava 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. 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 (@r-huijts/strava-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.