AI agents use updateActivity 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 falls under Write rather than Destructive because updates are reversible—the original activity data is modified in place and can typically be undone or re-edited by the user. It does not delete records (Destructive) or execute arbitrary code (Execute).
From the tool's definition Tool name 'updateActivity' and description 'Update an activity' indicate modification of existing data. Strava activities are user-generated fitness records (runs, rides, etc.).
Documented attack patterns abuse exactly the kind of access updateActivity 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 updateActivity:
{
"version": "1",
"default": "deny",
"tools": {
"updateActivity": {
"limits": [
{
"counter": "updateactivity_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}updateActivity 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.
Update an activity. 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 updateActivity: 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.
updateActivity 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 updateActivity 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 updateActivity. 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.
updateActivity 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.