Mark a recipe as having been made today (updates last made timestamp). Args: slug: The unique text identifier for the recipe. Returns: Dict[str, Any]: The updated recipe details.
AI agents use mark_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 modifies an existing recipe record by updating its 'last made' timestamp—a reversible write operation. It does not create new data (would be Write), delete anything (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial). The severity is low because the impact is limited to a non-critical metadata field on a single recipe, with no cascading effects or data loss risk.
From the tool's definition The tool 'mark_recipe_last_made' updates a timestamp field on a recipe record: 'updates last made timestamp' and 'Returns: The updated recipe details.' This is a metadata modification, not data creation/deletion.
Documented attack patterns abuse exactly the kind of access mark_recipe_last_made gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mealie MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mark_recipe_last_made:
{
"version": "1",
"default": "deny",
"tools": {
"mark_recipe_last_made": {
"limits": [
{
"counter": "mark_recipe_last_made_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mark_recipe_last_made stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Mark a recipe as having been made today (updates last made timestamp). Args: slug: The unique text identifier for the recipe. Returns: Dict[str, Any]: The updated recipe details. 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 mark_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.
mark_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 mark_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 mark_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.
mark_recipe_last_made is provided by the Mealie MCP Server MCP server (rldiao/mealie-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 44 Mealie MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
44 Mealie MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.