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 information about a routine folder without side effects. It is a simple GET operation that queries existing data. No data is created, modified, deleted, or financial operations are involved. The blast radius of misuse is minimal—an agent could only access routine folder metadata that the authenticated user already owns.
From the tool's definition Tool name 'get_routine_folder' and description 'Get a specific routine folder by ID' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get a specific routine folder by ID. 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 (srdjancodes/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 →