AI agents call get_running_streaks to retrieve information from Rewind without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical streak statistics from Strava (a fitness tracking service) and returns computed metrics. It retrieves data about the user's running activity without modifying, executing code, or triggering external operations. The minimal blast radius if misused is unauthorized data access, which is a confidentiality concern but not destructive or operational in nature.
From the tool's definition Tool name 'get_running_streaks' and description 'Get running streak data' indicate data retrieval only. The verb 'Get' and the passive framing ('current consecutive days', 'longest streak') show read-only operation with no modification, deletion, or execution…
Attacks that exploit this kind of access
Get running streak data from Strava -- current consecutive days with runs and the longest streak ever. It is categorised as a Read tool in the Rewind MCP Server, which means it retrieves data without modifying state.
Register the Rewind MCP server in PolicyLayer and add a rule for get_running_streaks: 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 Rewind. Nothing to install.
get_running_streaks 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_running_streaks 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_running_streaks. 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_running_streaks is provided by the Rewind MCP server (rewind-mcp-server). 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 →