get_running_stats

Get overall running statistics from Strava including total runs, distance, elevation, duration, average pace, and Eddington number.

Server Rewind rewind-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_running_stats does on Rewind

AI agents call get_running_stats 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.

Why get_running_stats needs a policy

This tool retrieves running statistics (total runs, distance, elevation, duration, average pace, Eddington number) from Strava. It is a pure read operation that queries existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker gains visibility into historical activity data but cannot alter or act on it. Classified as Read with low severity.

From the tool's definition Tool name is 'get_running_stats' and description states 'Get overall running statistics' — the verb 'Get' and action of retrieving aggregate statistics indicates data retrieval with no modification or side effects.

Questions about get_running_stats

What does the get_running_stats tool do? +

Get overall running statistics from Strava including total runs, distance, elevation, duration, average pace, and Eddington number. It is categorised as a Read tool in the Rewind MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_running_stats? +

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

What risk level is get_running_stats? +

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

Can I rate-limit get_running_stats? +

Yes. Add a rate_limit block to the get_running_stats 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 get_running_stats completely? +

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.