AI agents call get_routine_folder 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 or queries routine folder data from the Hevy fitness API with no side effects. It follows the Read category pattern of sibling get_* tools. The empty description slightly lowers confidence, but the clear intent and naming convention justify high confidence in the Read classification. No write, execute, destructive, or financial operations are implied.
From the tool's definition Tool name 'get_routine_folder' and context of sibling tools (all get_* operations) indicate data retrieval.
Documented attack patterns abuse exactly the kind of access get_routine_folder 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_folder:
{
"version": "1",
"default": "deny",
"tools": {
"get_routine_folder": {}
}
}get_routine_folder 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_folder. 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_folder: 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_folder 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_folder 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_folder. 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_folder 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.