AI agents use update_routine to create or update resources in Hevy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hevy environment.
The tool modifies existing routine data (reversible operation). Given the fitness tracking context and sibling tools that create and retrieve routines, this tool likely updates routine properties such as name, exercises, or schedule. This is a Write category action with medium severity because misuse could corrupt a user's workout routine data, but the effects are reversible through subsequent updates.
From the tool's definition Tool name 'update_routine' and server context indicate modification of fitness routine data. The empty description prevents certainty, but 'update' is a standard Write operation verb.
Documented attack patterns abuse exactly the kind of access update_routine gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hevy, and nothing reaches the server without passing your rules. This is the rule we recommend for update_routine:
{
"version": "1",
"default": "deny",
"tools": {
"update_routine": {
"limits": [
{
"counter": "update_routine_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_routine stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
update_routine. It is categorised as a Write tool in the Hevy 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. 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 (tomtorggler/hevy-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Hevy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Hevy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.