Formats a workout plan into a structured file format (currently supports Zwift .zwo)
AI agents use format-workout-file to create or update resources in Strava MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Strava MCP Server environment.
This tool creates/writes a structured file (Zwift .zwo format) from a workout plan. It produces a file output, which is a Write operation. The blast radius is low since it only creates a local workout file with no financial, destructive, or external execution implications.
From the tool's definition Formats a workout plan into a structured file format (currently supports Zwift .zwo)
Attacks that exploit this kind of access
Formats a workout plan into a structured file format (currently supports Zwift .zwo). It is categorised as a Write tool in the Strava MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Strava MCP Server MCP server in PolicyLayer and add a rule for format-workout-file: 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.
format-workout-file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the format-workout-file 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 format-workout-file. 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.
format-workout-file is provided by the Strava MCP Server MCP server (samitugal/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 →