Get history of a specific exercise across workouts.
AI agents call get_exercise_history to retrieve information from MCP Logger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries workout history data without creating, modifying, or deleting any records. It is a read-only operation with no destructive, financial, or code execution implications. The blast radius of misuse is minimal—an agent could only view exercise history, not alter or harm data or systems.
From the tool's definition Tool name 'get_exercise_history' and description 'Get history of a specific exercise across workouts' indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
Get history of a specific exercise across workouts. It is categorised as a Read tool in the MCP Logger MCP Server, which means it retrieves data without modifying state.
Register the MCP Logger MCP server in PolicyLayer and add a rule for get_exercise_history: 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 MCP Logger. Nothing to install.
get_exercise_history 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_history 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_history. 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_history is provided by the MCP Logger MCP server (johnzolton/mcp-logger). 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 →