Get full details of a specific workout including all exercises, sets, weights, reps, RPE, and block structure.
AI agents call get_workout_detail 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 queries and retrieves historical workout data. It performs no writes, deletions, code execution, or financial operations. The data returned is informational and used for tracking and analysis only. All sibling tools (get_* prefix) reinforce this server's read-only query pattern for fitness data.
From the tool's definition Tool name 'get_workout_detail' and description indicate data retrieval ('Get full details') with no modification or deletion. Returns workout metadata (exercises, sets, weights, reps, RPE, block structure) with no side effects.
Attacks that exploit this kind of access
Get full details of a specific workout including all exercises, sets, weights, reps, RPE, and block structure. 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_detail: 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_detail 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_detail 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_detail. 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_detail 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 →