get_trend_data_duckdb
AI agents call get_trend_data_duckdb to retrieve information from Apple Health MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve health trend data from a DuckDB backend, which is a read-only query operation. However, confidence is moderate (0.75) because the description is empty, preventing full assessment of scope and potential side effects.
From the tool's definition Tool name 'get_trend_data_duckdb' indicates data retrieval. Server description emphasizes 'query, analyze' operations on Apple Health records. No modification, deletion, or execution keywords present.
Attacks that exploit this kind of access
get_trend_data_duckdb. It is categorised as a Read tool in the Apple Health MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apple Health MCP Server MCP server in PolicyLayer and add a rule for get_trend_data_duckdb: 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 Apple Health MCP Server. Nothing to install.
get_trend_data_duckdb 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_trend_data_duckdb 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_trend_data_duckdb. 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_trend_data_duckdb is provided by the Apple Health MCP Server MCP server (the-momentum/apple-health-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.