Returns 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 information about segment efforts for the authenticated athlete. It has no side effects—it only queries and returns data without modifying, deleting, or executing operations. The blast radius of misuse is minimal since it only exposes the user's own activity data that they have already authorized the tool to access.
From the tool's definition Tool name 'list-segment-efforts' and description 'Returns the authenticated athlete' indicate data retrieval. The Strava MCP context (query activities, stats, routes, segments using natural language) confirms this is a query/read operation.
Attacks that exploit this kind of access
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 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 (samitugal/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 →