Create a new workout
AI agents use createWorkout to create or update resources in Hevy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hevy MCP Server environment.
This tool creates new workout records in the Hevy fitness platform. Creation operations are Write-category actions as they add new data reversibly (the created workout can later be modified or deleted). Severity is medium because misuse could result in spam/pollution of user workout data, but the impact is limited to the user's own fitness records and there are no irreversible consequences or financial implications.
From the tool's definition Tool name 'createWorkout' combined with description 'Create a new workout' indicates data creation. The Hevy API context shows this is a fitness tracking platform where workouts are user records that can be created and modified.
Attacks that exploit this kind of access
Create a new workout. It is categorised as a Write tool in the Hevy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hevy MCP Server MCP server in PolicyLayer and add a rule for createWorkout: 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 Hevy MCP Server. Nothing to install.
createWorkout 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 createWorkout 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 createWorkout. 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.
createWorkout is provided by the Hevy MCP Server MCP server (jcjiron/hevy-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 →