AI agents use disconnect-strava 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 application state by removing stored credentials and disconnecting the user's Strava account. While it does not delete user data on Strava's servers, it irreversibly changes the local authentication configuration. This is a Write action rather than Destructive because the action can be reversed (user can reconnect), and the core user data remains intact.
From the tool's definition The tool description states it will 'Disconnect your Strava account and remove stored credentials', which involves modifying the stored authentication state and connection data.
Attacks that exploit this kind of access
Disconnect your Strava account and remove stored credentials. Use this when the user wants to logout, disconnect, or remove their Strava connection. 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 disconnect-strava: 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.
disconnect-strava 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 disconnect-strava 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 disconnect-strava. 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.
disconnect-strava 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.