Return weekly calorie and protein averages, best day, and tracked-day count.
AI agents call get_weekly_summary to retrieve information from Nutrition MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical nutrition data to compute and display summary statistics. It has no capacity to modify, delete, or execute operations. The information returned is purely for analysis and reporting purposes, making it a straightforward Read operation with minimal risk.
From the tool's definition Tool returns aggregated weekly statistics (calorie and protein averages, best day, tracked-day count) with no modification or deletion of data. The verb 'Return' and the read-only nature of summary metrics confirm data retrieval without side effects.
Attacks that exploit this kind of access
Return weekly calorie and protein averages, best day, and tracked-day count. It is categorised as a Read tool in the Nutrition MCP MCP Server, which means it retrieves data without modifying state.
Register the Nutrition MCP server in PolicyLayer and add a rule for get_weekly_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 Nutrition MCP. Nothing to install.
get_weekly_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_weekly_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_weekly_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_weekly_summary is provided by the Nutrition MCP server (ronkommoji/nutrition-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 →