Summary of all activities from the past 7 days.
AI agents call weekly_summary to retrieve information from Strava MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries aggregated fitness data from the past week and returns a summary view. It is a read-only operation that retrieves existing data without creating, modifying, deleting, or executing any operations. The low severity reflects minimal blast radius—misuse would only expose historical activity summaries already accessible to the authenticated user.
From the tool's definition Tool name and description: 'weekly_summary' that retrieves a 'Summary of all activities from the past 7 days.' This is a data retrieval operation with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Summary of all activities from the past 7 days. It is categorised as a Read tool in the Strava MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Strava MCP Server MCP server in PolicyLayer and add a rule for weekly_summary: 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 MCP Server. Nothing to install.
weekly_summary 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 weekly_summary 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 weekly_summary. 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.
weekly_summary is provided by the Strava MCP Server MCP server (manojanasuri16/strava-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 →