clear_whoop_cache

THE RISK

Critical Risk

Why clear_whoop_cache needs a policy

The tool irreversibly deletes locally cached fitness data. While the data itself can be re-fetched from the WHOOP API, the cached state is permanently destroyed and cannot be undone without re-fetching. Blast radius is low since only local cache is affected and no financial, system-critical, or user-generated data is at risk.

From the tool's definition 'Clear all cached WHOOP data' — permanently removes locally cached data, forcing fresh API calls. The word 'clear' implies irreversible deletion of stored cache contents.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access clear_whoop_cache gives an agent:

POLICY

How to control clear_whoop_cache

PolicyLayer is an MCP gateway — it sits between your AI agents and WHOOP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_whoop_cache:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_whoop_cache"
  ]
}

clear_whoop_cache disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register WHOOP MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More WHOOP MCP Server tools

Read get_whoop_auth_status Get WHOOP authentication status and connection info Read get_whoop_cycles Get WHOOP physiological cycle data (daily summaries) with optional date range and limit Read get_whoop_profile Get WHOOP user profile information including name and basic details Read get_whoop_recovery Get WHOOP recovery data with optional date range and limit Read get_whoop_sleep Get WHOOP sleep data with optional date range and limit Read get_whoop_workouts Get WHOOP workout data with optional date range and limit

All 7 WHOOP MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in WHOOP MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about clear_whoop_cache

What does the clear_whoop_cache tool do? +

Clear all cached WHOOP data to force fresh API calls. 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.

How do I enforce a policy on clear_whoop_cache? +

Register the WHOOP MCP Server MCP server in PolicyLayer and add a rule for clear_whoop_cache: 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.

What risk level is clear_whoop_cache? +

clear_whoop_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_whoop_cache? +

Yes. Add a rate_limit block to the clear_whoop_cache 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.

How do I block clear_whoop_cache completely? +

Set action: deny in the PolicyLayer policy for clear_whoop_cache. 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.

What MCP server provides clear_whoop_cache? +

clear_whoop_cache is provided by the WHOOP MCP Server MCP server (romanevstigneev/whoop-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WHOOP MCP Server tool call.

Start from WHOOP MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →