AI agents use createRoute 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 creates a new route object in Strava, which is a reversible data modification. It does not execute arbitrary code, delete data irreversibly, or commit financial transactions. While it modifies user data, the action can be undone (route can be deleted). Severity is medium because misuse could create numerous unwanted routes cluttering a user's Strava account, but the impact is limited and reversible.
From the tool's definition Tool name is 'createRoute' with description 'Create a route', indicating data creation on the Strava platform. Sibling tools like 'createActivity', 'createUpload', and 'deleteActivity' confirm this server performs user data modifications.
Documented attack patterns abuse exactly the kind of access createRoute 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 createRoute:
{
"version": "1",
"default": "deny",
"tools": {
"createRoute": {
"limits": [
{
"counter": "createroute_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createRoute 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.
Create a route. 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 createRoute: 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.
createRoute 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 createRoute 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 createRoute. 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.
createRoute 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.