Get user information from Withings account
AI agents call get_user_info to retrieve information from Withings MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user account information from the Withings Health API. It is a read-only operation that queries data without side effects, modifications, or destructive actions. The severity is low because user profile information is generally non-sensitive health metadata (name, email, etc.), and exposure does not enable financial transactions, code execution, or irreversible changes.
From the tool's definition Tool name is 'get_user_info' and description states 'Get user information from Withings account' — a retrieval operation with no modification or deletion capability.
Attacks that exploit this kind of access
Get user information from Withings account. It is categorised as a Read tool in the Withings MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Withings MCP Server MCP server in PolicyLayer and add a rule for get_user_info: 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 Withings MCP Server. Nothing to install.
get_user_info 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_info 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_info. 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_info is provided by the Withings MCP Server MCP server (schimmilab/withings-mcp-server). 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 →