AI agents use starSegment 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) which is a reversible write operation with minimal blast radius. It does not delete data, execute code, or involve financial transactions.
From the tool's definition 'Star or unstar a segment' — toggles a bookmark/favorite state on a segment
Documented attack patterns abuse exactly the kind of access starSegment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Strava, and nothing reaches the server without passing your rules. This is the rule we recommend for starSegment:
{
"version": "1",
"default": "deny",
"tools": {
"starSegment": {
"limits": [
{
"counter": "starsegment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}starSegment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Star or unstar a segment. 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 starSegment: 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.
starSegment 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 starSegment 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 starSegment. 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.
starSegment is provided by the Strava MCP server (kw510/strava-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Strava, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 Strava tools catalogued and risk-classified — across an index of 43,000+ MCP servers.