whoop_authenticate · Health MCP Server MCP: Risk & Policy

WHAT IT DOES

What whoop_authenticate does on Health MCP Server

AI agents invoke whoop_authenticate to trigger actions in Health MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why whoop_authenticate needs a policy

This tool triggers an external browser action and OAuth flow, which constitutes executing an external operation (opening a browser window and initiating an authorization sequence). It is not purely a read or write operation — it drives a real-world browser interaction whose effects depend on the execution context.

From the tool's definition Opens a browser window for OAuth login to authorize access to your health data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

whoop_authenticate Rate-limited

whoop_authenticate stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "whoop_authenticate": {
      "limits": [
        {
          "counter": "whoop_authenticate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Health MCP Server, so you can run agents against it safely.

FAQ

Questions about whoop_authenticate

What does the whoop_authenticate tool do? +

Authenticate with Whoop. Opens a browser window for OAuth login to authorize access to your health data. It is categorised as a Execute tool in the Health MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on whoop_authenticate? +

Register the Health MCP Server MCP server in PolicyLayer and add a rule for whoop_authenticate: 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 Health MCP Server. Nothing to install.

What risk level is whoop_authenticate? +

whoop_authenticate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit whoop_authenticate? +

Yes. Add a rate_limit block to the whoop_authenticate 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 whoop_authenticate completely? +

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

whoop_authenticate is provided by the Health MCP Server MCP server (marholoubek/health_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.