Get weekly calorie consumption report
AI agents call get_weekly_report to retrieve information from Daily Calorie Tracker MCP Server 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 calorie tracking data for reporting purposes. It has no side effects, does not modify persistent state, and does not execute code or trigger external operations. It is clearly a read-only operation that falls squarely within the 'Read' category.
From the tool's definition Tool name 'get_weekly_report' and description 'Get weekly calorie consumption report' indicate data retrieval only. It queries historical calorie data to generate a summary report without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get weekly calorie consumption report. It is categorised as a Read tool in the Daily Calorie Tracker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Daily Calorie Tracker MCP Server MCP server in PolicyLayer and add a rule for get_weekly_report: 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 Daily Calorie Tracker MCP Server. Nothing to install.
get_weekly_report 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_report 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_report. 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_report is provided by the Daily Calorie Tracker MCP Server MCP server (veriteknik/daily-calorie-tracker). 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 →