Get daily activity summary for a date or date range
AI agents call get_daily_summary 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 pre-computed summary data from the Zepp Life health database for specified dates. It has no side effects, does not modify data, execute code, or involve financial operations. It is a straightforward query/fetch operation consistent with other read-only tools on this server (get_connection_status, query_heart_rate, query_sleep, etc.).
From the tool's definition Tool name 'get_daily_summary' and description 'Get daily activity summary for a date or date range' indicate a retrieval operation with no modification or execution of external code. The verb 'get' is characteristic of read-only operations.
Attacks that exploit this kind of access
Get daily activity summary for a date or 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 get_daily_summary: 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.
get_daily_summary 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_daily_summary 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_daily_summary. 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_daily_summary 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 →