Query body measurements (weight, body composition) for a date range
AI agents call query_body_measurements to retrieve information from Zepp Life MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical health data (body measurements) within a specified date range. It has no side effects, does not modify or delete data, and does not execute external operations or commit financial obligations. It is a straightforward read operation consistent with other query tools on the same server (query_heart_rate, query_sleep, query_workouts).
From the tool's definition Tool name is 'query_body_measurements' and description states it 'Query[s] body measurements (weight, body composition) for a date range' — a retrieval operation with no modification or deletion capability.
Attacks that exploit this kind of access
Query body measurements (weight, body composition) for a date range. It is categorised as a Read tool in the Zepp Life MCP MCP Server, which means it retrieves data without modifying state.
Register the Zepp Life MCP server in PolicyLayer and add a rule for query_body_measurements: 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 Zepp Life MCP. Nothing to install.
query_body_measurements 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 query_body_measurements 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 query_body_measurements. 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.
query_body_measurements is provided by the Zepp Life MCP server (kubulashvili/zepp-life-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 →