Update an existing food.
AI agents use mealie_foods_update to create or update resources in Mealie MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mealie MCP Server environment.
The tool modifies existing data (food items) reversibly—updates can be undone or corrected through subsequent updates or rollbacks. This is characteristic of Write operations. Severity is medium because corrupting food data in a recipe system could affect meal plans and nutritional information, but the impact is limited to a single user's food database and is reversible.
From the tool's definition Tool name 'mealie_foods_update' and description 'Update an existing food' indicate a modification operation on food data within the Mealie recipe management system.
Attacks that exploit this kind of access
Update an existing food. It is categorised as a Write tool in the Mealie MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for mealie_foods_update: 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 Mealie MCP Server. Nothing to install.
mealie_foods_update 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 mealie_foods_update 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 mealie_foods_update. 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.
mealie_foods_update is provided by the Mealie MCP Server MCP server (mdlopresti/mealie-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 →