AI agents call get_routine to retrieve information from Hevy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves routine data from the Hevy fitness API with no side effects. The 'get_' prefix is a standard convention for read operations that query and return data without modification.
From the tool's definition Tool name 'get_routine' and sibling tools 'get_routines', 'get_exercise_history', 'get_exercise_template', 'get_exercise_templates' all follow the 'get_*' pattern indicating data retrieval operations.
Documented attack patterns abuse exactly the kind of access get_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 get_routine:
{
"version": "1",
"default": "deny",
"tools": {
"get_routine": {}
}
}get_routine is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_routine. It is categorised as a Read tool in the Hevy MCP Server, which means it retrieves data without modifying state.
Register the Hevy MCP server in PolicyLayer and add a rule for get_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.
get_routine is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.