AI agents call get_personal_records 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 retrieves personal running statistics from Strava (a fitness tracking platform). It queries and returns historical performance data without creating, modifying, deleting, or executing any operations. The data retrieved is informational only. While it accesses personal data, it does so read-only, making it a Read category tool with low severity since misuse would only expose fitness statistics.
From the tool's definition Tool name 'get_personal_records' and description 'Get personal running records (PRs) from Strava -- fastest times at standard distances' indicates retrieval of existing historical running data without modification or side effects.
Attacks that exploit this kind of access
Get personal running records (PRs) from Strava -- fastest times at standard distances like mile, 5K, 10K, half marathon, marathon. 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_personal_records: 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_personal_records 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_personal_records 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_personal_records. 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_personal_records 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 →