Get Strava athlete profile including all-time stats, year-to-date totals, and gear (bikes, shoes).
AI agents call get_strava_profile to retrieve information from Health MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Strava profile information without modifying any data or triggering side effects. It aggregates read-only fitness metrics and equipment details. The only risk is information disclosure of fitness data already associated with the connected Strava account, which is inherent to the server's purpose and poses minimal security risk if the integration is authorized.
From the tool's definition Tool retrieves athlete profile data including stats, totals, and gear information. Verbs 'Get' and actions are purely informational with no mutations, no code execution, no data deletion, and no financial operations.
Attacks that exploit this kind of access
Get Strava athlete profile including all-time stats, year-to-date totals, and gear (bikes, shoes). It is categorised as a Read tool in the Health MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Health MCP Server MCP server in PolicyLayer and add a rule for get_strava_profile: 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 Health MCP Server. Nothing to install.
get_strava_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_strava_profile 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 get_strava_profile. 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.
get_strava_profile is provided by the Health MCP Server MCP server (marholoubek/health_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 →