Get user profile including name, email, and body measurements (height, weight, max heart rate) from Whoop.
AI agents call get_user_profile to retrieve information from Health MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries personal health profile information without side effects. While it accesses personally identifiable information (name, email) and biometric data (height, weight, max heart rate), it is purely a read operation with no capability to modify, delete, or trigger external actions.
From the tool's definition Tool retrieves user profile data including name, email, and body measurements from Whoop; uses verb 'Get' indicating data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Get user profile including name, email, and body measurements (height, weight, max heart rate) from Whoop. It is categorised as a Read tool in the Health MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Health MCP Server MCP server in PolicyLayer and add a rule for 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 Health MCP Server. Nothing to install.
get_user_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
get_user_profile 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.
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 →