Link detailed exercises to an existing Whoop activity with per-set granularity.
AI agents use link_exercises to create or update resources in Whoop MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Whoop MCP Server environment.
The tool creates or updates exercise associations within an activity record (Write category). Severity is medium because misuse could pollute health tracking data, but the effect is reversible (exercises can be unlinked or corrected). It lacks the destructive finality of deletion, the code execution risk of Execute, or financial impact.
From the tool's definition Tool enables linking/attaching exercises to an existing activity, which modifies activity records with exercise details 'with per-set granularity'—a reversible data modification operation.
Attacks that exploit this kind of access
Link detailed exercises to an existing Whoop activity with per-set granularity. It is categorised as a Write tool in the Whoop MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Whoop MCP Server MCP server in PolicyLayer and add a rule for link_exercises: 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 Whoop MCP Server. Nothing to install.
link_exercises is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the link_exercises 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 link_exercises. 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.
link_exercises is provided by the Whoop MCP Server MCP server (jd1207/whoop-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 →