Create a new routine folder
AI agents use createRoutineFolder to create or update resources in Hevy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hevy MCP Server environment.
The tool creates a new organizational structure (routine folder) in the fitness tracking system. This is a standard Write category action: it creates data that can be modified or deleted later. The operation has minimal blast radius—a misused folder creation would simply create unwanted folder structures that can be cleaned up. No code execution, financial impact, or data deletion is involved.
From the tool's definition Tool name 'createRoutineFolder' and description 'Create a new routine folder' indicate creation of a new data object in the Hevy fitness platform.
Attacks that exploit this kind of access
Create a new routine folder. It is categorised as a Write tool in the Hevy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hevy MCP Server MCP server in PolicyLayer and add a rule for createRoutineFolder: 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 Server. Nothing to install.
createRoutineFolder 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 createRoutineFolder 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 createRoutineFolder. 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.
createRoutineFolder is provided by the Hevy MCP Server MCP server (jcjiron/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 →