List segments starred by the authenticated athlete
AI agents call list_starred_segments 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 queries and retrieves user preference data (starred segments) from the Strava API. It performs no side effects, does not modify data, execute code, delete anything, or involve financial transactions. The blast radius of misuse is minimal—an attacker could only view which segments an athlete has starred, which is limited to the authenticated user's own preferences.
From the tool's definition Tool retrieves 'segments starred by the authenticated athlete' - a read-only query operation that returns existing data without modifying or executing any actions.
Attacks that exploit this kind of access
List segments starred by 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_starred_segments: 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_starred_segments 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_starred_segments 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_starred_segments. 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_starred_segments is provided by the Strava MCP Server MCP server (juanlarreapm/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 →