Update the recipe last-made timestamp (ISO datetime string).
AI agents use update_recipe_last_made 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.
This tool creates or modifies data (a timestamp field) in a reversible manner. Users can update the timestamp again to any value, so the change is not permanent or destructive. The blast radius is minimal—updating a metadata field does not affect recipe content, meal plans, or data integrity. This is a typical Write operation.
From the tool's definition Tool name contains 'update' and description states 'Update the recipe last-made timestamp', which modifies a timestamp field on a recipe record.
Attacks that exploit this kind of access
Update the recipe last-made timestamp (ISO datetime string). 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 update_recipe_last_made: 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.
update_recipe_last_made 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 update_recipe_last_made 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 update_recipe_last_made. 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.
update_recipe_last_made is provided by the Mealie MCP Server MCP server (nikopol666/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 →