Fetches detailed information about a specific activity using its ID.
AI agents call get-activity-details 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 retrieves and queries activity data from Strava without creating, modifying, or deleting any information. It is a straightforward read operation that returns athlete's own fitness/activity data. The blast radius of misuse is minimal—an agent could only access activity details the authenticated user already owns. No financial, destructive, or execute risks present.
From the tool's definition Tool name 'get-activity-details' and description 'Fetches detailed information about a specific activity using its ID' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Fetches detailed information about a specific activity using its ID. 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 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 Strava MCP Server. 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 Strava MCP Server MCP server (limeon-source/strava-mcp). 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 →