AI agents use update_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.
The 'update_routine' prefix indicates data modification. While the description is empty (lowering confidence slightly), the pattern of sibling tools and the server's documented capability to 'manage routines' confirms this creates or modifies workout routine records reversibly.
From the tool's definition Tool name is 'update_routine' with no description provided. Based on sibling tools (create_routine, create_workout, update_workout) and the server's stated purpose of 'manage routines and exercises' through 'logging new fitness sessions,' this tool modifies…
Attacks that exploit this kind of access
update_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 update_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.
update_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 update_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 update_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.
update_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.
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 →