Get aggregate nutrition data over a date range with trends and insights.
AI agents call get_date_range_summary to retrieve information from Myfitnesspal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates existing nutrition data over a time period, computing trends and insights from historical records. There are no side effects, no data modification, no code execution, and no destructive operations. The blast radius of misuse is minimal—an agent could only access the user's own historical nutrition data they have already logged.
From the tool's definition Tool name contains 'get_', description states 'Get aggregate nutrition data' - purely retrieves and queries historical nutrition information with no modification capability.
Attacks that exploit this kind of access
Get aggregate nutrition data over a date range with trends and insights. It is categorised as a Read tool in the Myfitnesspal MCP Server, which means it retrieves data without modifying state.
Register the Myfitnesspal MCP server in PolicyLayer and add a rule for get_date_range_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 Myfitnesspal. Nothing to install.
get_date_range_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_date_range_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_date_range_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_date_range_summary is provided by the Myfitnesspal MCP server (linares222/mcp-myfitnesspal). 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 →