Get progress history for specific exercises between start and end dates. Returns exercise data including weights, reps, and sets for each workout. Results are ordered by date descending. Useful for tracking progress over time for particular exercises. Example: {
AI agents call get-exercise-progress-by-ids 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.
Even though get-exercise-progress-by-ids only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Get progress history for specific exercises between start and end dates. Returns exercise data including weights, reps, and sets for each workout. Results are ordered by date descending. Useful for tracking progress over time for particular exercises. Example: {. 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-exercise-progress-by-ids: 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-exercise-progress-by-ids 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-exercise-progress-by-ids 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-exercise-progress-by-ids. 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-exercise-progress-by-ids is provided by the Hevy MCP server (vreippainen/hevy-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.