AI agents use create_routine to create or update resources in Hevy MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hevy MCP environment.
This tool creates new workout routine data in the user's Hevy account. While creation is reversible (routines can be deleted or modified), it modifies user data persistently. This is a Write operation rather than Read (no data retrieval), Execute (no code/command execution), or Destructive (data is not irreversibly deleted).
From the tool's definition Tool name 'create_routine' indicates creation of a new fitness routine in the Hevy workout tracking app. Tool description is empty, but the server description states the tool 'enables...managing routines' and sibling tools include 'update_routine' and…
Attacks that exploit this kind of access
create_routine. It is categorised as a Write tool in the Hevy MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hevy MCP server in PolicyLayer and add a rule for create_routine: 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. Nothing to install.
create_routine 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_routine 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_routine. 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_routine is provided by the Hevy MCP server (zachsai/hevy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
create_routine is one line of Hevy's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →