Connect your Strava account to enable activity tracking. This will open a browser window for secure authentication. Use this when the user asks to connect, link, or authenticate their Strava account.
AI agents invoke connect-strava to trigger actions in Strava MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes an external operation (opening a browser window) and initiates an OAuth authentication flow with Strava. While it doesn't modify or delete data, it triggers a side-effecting external process that goes beyond simple data retrieval. The blast radius is medium since misuse could link an unintended Strava account or initiate unauthorized authentication flows.
From the tool's definition 'This will open a browser window for secure authentication' — triggers an external browser operation and OAuth authentication flow
Attacks that exploit this kind of access
Connect your Strava account to enable activity tracking. This will open a browser window for secure authentication. Use this when the user asks to connect, link, or authenticate their Strava account. It is categorised as a Execute tool in the Strava MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Strava MCP Server MCP server in PolicyLayer and add a rule for connect-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 MCP Server. Nothing to install.
connect-strava is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the connect-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 connect-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.
connect-strava is provided by the Strava MCP Server MCP server (samitugal/strava-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →