Check the processing status of an upload. Returns status, error info, and the resulting activity ID once complete.
AI agents call strava_get_upload 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 is a read-only status check operation. It queries the state of an existing upload and returns metadata (status, error details, activity ID) without side effects. No data is created, modified, deleted, or executed. Even though uploads can represent data submission, this specific tool only observes their state.
From the tool's definition Tool name contains 'get' and description states it 'Check the processing status' and 'Returns status, error info, and the resulting activity ID' — purely retrieves state information without modifying or triggering any actions.
Attacks that exploit this kind of access
Check the processing status of an upload. Returns status, error info, and the resulting activity ID once complete. 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 strava_get_upload: 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.
strava_get_upload 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 strava_get_upload 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 strava_get_upload. 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.
strava_get_upload is provided by the Strava MCP Server MCP server (justmytwospence/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 →