Get a specific segment effort by ID, including elapsed time, heart rate, watts, and achievements.
AI agents call strava_get_segment_effort to retrieve information from Strava MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only retrieval operation that queries existing fitness data from the Strava API. It returns performance information without creating, modifying, deleting, or executing any external operations. The tool has minimal security risk as it only accesses the user's own activity data.
From the tool's definition Tool retrieves ('Get') a specific segment effort by ID and returns performance metrics (elapsed time, heart rate, watts, achievements) with no modification or side effects described.
Attacks that exploit this kind of access
Get a specific segment effort by ID, including elapsed time, heart rate, watts, and achievements. It is categorised as a Read tool in the Strava MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Strava MCP Server MCP server in PolicyLayer and add a rule for strava_get_segment_effort: 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.
strava_get_segment_effort 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 strava_get_segment_effort 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 strava_get_segment_effort. 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.
strava_get_segment_effort is provided by the Strava MCP Server MCP server (justmytwospence/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 →