AI agents use star-segment to create or update resources in Strava — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Strava environment.
This tool modifies a user preference (starring/unstarring a segment) in Strava. It creates or modifies data reversibly — the action can be undone by starring/unstarring again. No data is deleted, no code is executed, and no financial transactions occur. Blast radius is minimal as it only affects the user's starred segments list.
From the tool's definition Stars or unstars a specific segment for the authenticated athlete
Attacks that exploit this kind of access
Stars or unstars a specific segment for the authenticated athlete. It is categorised as a Write tool in the Strava MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Strava MCP server in PolicyLayer and add a rule for star-segment: 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.
star-segment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the star-segment 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 star-segment. 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.
star-segment 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.