getSegmentEffortStreams

THE RISK

Low Risk

Why getSegmentEffortStreams needs a policy

This tool reads/retrieves data about a specific segment effort from Strava. It has no side effects, does not modify data, and simply fetches stream data (e.g., GPS, speed, power data) associated with a segment effort.

From the tool's definition 'Get streams for a specific segment effort' - retrieves streaming data for a segment effort

Documented attack patterns abuse exactly the kind of access getSegmentEffortStreams gives an agent:

POLICY

How to control getSegmentEffortStreams

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 getSegmentEffortStreams:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getSegmentEffortStreams": {}
  }
}

getSegmentEffortStreams is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Strava — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Strava tools

Destructive deleteActivity Delete an activity Write starSegment Star or unstar a segment Write createActivity Create a new activity on Strava Write createRoute Create a route Write createUpload Upload an activity Write updateActivity Update an activity Write updateLoggedInAthlete Update the currently authenticated athlete Read exploreSegments Explore segments

All 37 Strava tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about getSegmentEffortStreams

What does the getSegmentEffortStreams tool do? +

Get streams for a specific segment effort. It is categorised as a Read tool in the Strava MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getSegmentEffortStreams? +

Register the Strava MCP server in PolicyLayer and add a rule for getSegmentEffortStreams: 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.

What risk level is getSegmentEffortStreams? +

getSegmentEffortStreams is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getSegmentEffortStreams? +

Yes. Add a rate_limit block to the getSegmentEffortStreams 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.

How do I block getSegmentEffortStreams completely? +

Set action: deny in the PolicyLayer policy for getSegmentEffortStreams. 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.

What MCP server provides getSegmentEffortStreams? +

getSegmentEffortStreams 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.

Enforce policy on every Strava tool call.

Start from Strava, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →