create_workout
AI agents use create_workout to create or update resources in FitnessMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FitnessMCP environment.
This tool creates workout data, which is a reversible write operation. It does not execute arbitrary code, delete data, or commit financial transactions. The severity is medium because misconfigured or malicious workouts could inflate fitness records or mislead health tracking, but the impact is limited to the user's own fitness data and reversible through deletion or correction.
From the tool's definition Tool name 'create_workout' indicates creation of a new workout entry. Sibling tools like 'create_exercise_template', 'create_routine', and 'cronometer_add_food_entry' are all write operations that create or modify data.
Attacks that exploit this kind of access
create_workout. It is categorised as a Write tool in the FitnessMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fitness MCP server in PolicyLayer and add a rule for create_workout: 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 FitnessMCP. Nothing to install.
create_workout 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 create_workout 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 create_workout. 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.
create_workout is provided by the Fitness MCP server (senoj100-alt/fitnessmcp). 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 →