whoop-get-user-profile

THE RISK

Low Risk

Why whoop-get-user-profile needs a policy

This tool only retrieves basic, non-sensitive user profile data (name, email) for an already-authenticated user. It is a straightforward query operation with read-only semantics and minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'whoop-get-user-profile' and description 'Get basic user profile information (name, email) for the authenticated user' indicate a retrieval operation with no modifications or side effects.

Documented attack patterns abuse exactly the kind of access whoop-get-user-profile gives an agent:

POLICY

How to control whoop-get-user-profile

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 whoop-get-user-profile:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "whoop-get-user-profile": {}
  }
}

whoop-get-user-profile is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More WHOOP MCP Server tools

Destructive whoop-revoke-user-access Revoke the access token granted by the user Write whoop-refresh-token Refresh access token using refresh token Write whoop-set-access-token Set the access token for API calls Read whoop-exchange-code-for-token Exchange authorization code for access token Read whoop-get-authorization-url Get the authorization URL for OAuth flow Read whoop-get-cycle-by-id Get the cycle for the specified ID Read whoop-get-cycle-collection Get all physiological cycles for a user, paginated Read whoop-get-recovery-collection Get all recovery data for a user, paginated

All 16 WHOOP MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about whoop-get-user-profile

What does the whoop-get-user-profile tool do? +

Get basic user profile information (name, email) for the authenticated user. It is categorised as a Read tool in the WHOOP MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on whoop-get-user-profile? +

Register the WHOOP MCP Server MCP server in PolicyLayer and add a rule for whoop-get-user-profile: 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 whoop-get-user-profile? +

whoop-get-user-profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit whoop-get-user-profile? +

Yes. Add a rate_limit block to the whoop-get-user-profile 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-get-user-profile completely? +

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

whoop-get-user-profile is provided by the WHOOP MCP Server MCP server (nissand/whoop-mcp-server-claude). 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 →