Delete a nutrition day and optionally cascade to meals/items.
AI agents call delete_nutrition_day to permanently remove resources in MCP Logger — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes nutrition tracking data from the database with cascading deletions to related meal records. The operation cannot be undone and represents loss of user-tracked health information. While not critical (no financial or security system impact), the irreversible data destruction and cascade behavior warrants Destructive classification over Write or Execute.
From the tool's definition Tool name includes 'delete' and description states 'Delete a nutrition day and optionally cascade to meals/items' — irreversible removal of data records.
Attacks that exploit this kind of access
Delete a nutrition day and optionally cascade to meals/items. It is categorised as a Destructive tool in the MCP Logger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Logger MCP server in PolicyLayer and add a rule for delete_nutrition_day: 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 MCP Logger. Nothing to install.
delete_nutrition_day is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_nutrition_day 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 delete_nutrition_day. 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.
delete_nutrition_day is provided by the MCP Logger MCP server (johnzolton/mcp-logger). 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 →