AI agents call get_activity_details 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 is a read-only operation that queries and retrieves existing personal activity data. It has no side effects, does not modify or delete data, and does not execute external operations. The tool simply fetches and returns information about a user's activity record, consistent with the 'Read' category for retrieval operations with no side effects.
From the tool's definition Tool retrieves detailed information about a specific running activity by ID, including distance, pace, heart rate, elevation, calories, and a Strava resource link. No modification, deletion, or execution capabilities are implied.
Attacks that exploit this kind of access
Get detailed information about a specific running activity by ID, including distance, pace, heart rate, elevation, calories, and a Strava resource link. 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_activity_details: 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_activity_details 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_activity_details 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_activity_details. 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_activity_details 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 →