Get recent workout history with optional filtering by date range or category. Returns workout summaries including date, exercises performed, duration, and completion status.
AI agents call get_workout_history to retrieve information from Iridium MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical workout data with optional filtering. It has no side effects, does not modify any data, and does not execute external operations. The only parameters are read-only filters (date range, category). The blast radius of misuse is minimal—an agent could only retrieve existing fitness data that the user has access to through normal Iridium API permissions.
From the tool's definition Tool name 'get_workout_history' and description 'Get recent workout history' with 'Returns workout summaries' indicates data retrieval only. No modification, deletion, execution, or financial operations are mentioned.
Attacks that exploit this kind of access
Get recent workout history with optional filtering by date range or category. Returns workout summaries including date, exercises performed, duration, and completion status. It is categorised as a Read tool in the Iridium MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Iridium MCP Server MCP server in PolicyLayer and add a rule for get_workout_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 Iridium MCP Server. Nothing to install.
get_workout_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_workout_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_workout_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_workout_history is provided by the Iridium MCP Server MCP server (rostehea/iridium-mcp-server). 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 →