Create or update a nutrition day entry.
AI agents use upsert_nutrition_day to create or update resources in MCP Logger — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Logger environment.
This tool creates new or modifies existing nutrition day records in the SQLite database. These are reversible changes—entries can be updated again or deleted via the delete_nutrition_day tool on the same server. It does not execute arbitrary code, destroy data permanently, or move money.
From the tool's definition Tool name 'upsert_nutrition_day' and description 'Create or update a nutrition day entry' indicate reversible data modification. 'Upsert' is a standard database operation combining insert and update, which are Write operations.
Attacks that exploit this kind of access
Create or update a nutrition day entry. It is categorised as a Write tool in the MCP Logger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Logger MCP server in PolicyLayer and add a rule for upsert_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.
upsert_nutrition_day is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the upsert_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 upsert_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.
upsert_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 →