AI agents call deleteActivity to permanently remove resources in Strava — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of activities is a destructive action that cannot be undone. While the blast radius is limited to a single user's Strava account (not system-wide), deleting user-created activities represents permanent data loss. This warrants 'high' severity rather than 'critical' because the impact is scoped to individual activities rather than bulk data or critical infrastructure.
From the tool's definition Tool name is 'deleteActivity' with description 'Delete an activity'. The verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access deleteActivity 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 deleteActivity:
{
"version": "1",
"default": "deny",
"hide": [
"deleteActivity"
]
}deleteActivity disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an activity. It is categorised as a Destructive tool in the Strava MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Strava MCP server in PolicyLayer and add a rule for deleteActivity: 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.
deleteActivity is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteActivity 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 deleteActivity. 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.
deleteActivity 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.