Delete an activity from Whoop. Use list_activities to find the ID first.
AI agents call delete_activity to permanently remove resources in Whoop MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of activity records cannot be undone and represents permanent loss of user health/fitness data. While the blast radius is somewhat limited to a single user's activity log (not system-wide or financial), the irreversible nature of deletion and the sensitivity of health data warrant 'high' severity. This is a clear Destructive category case per the rubric.
From the tool's definition Tool name is 'delete_activity' and description states 'Delete an activity from Whoop'—the verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete an activity from Whoop. Use list_activities to find the ID first. It is categorised as a Destructive tool in the Whoop MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Whoop MCP Server MCP server in PolicyLayer and add a rule for delete_activity: 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.
delete_activity is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_activity 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 delete_activity. 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.
delete_activity 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 →