Create a new meal plan entry. Args: date: Date for the mealplan in ISO format (YYYY-MM-DD) recipe_id: UUID of the recipe to add to the mealplan (optional) title: Title for the mealplan entry if not using a recipe (optional) entry_type: Type of mealplan entry (breakfast, lunch, dinner, side) Retur...
AI agents use create_mealplan 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 new meal plan records in the Mealie database. Creation is a reversible modification (meal plans can be deleted or edited), making it Write rather than Destructive. The blast radius is minimal—an AI agent misusing this could create unwanted meal plan entries, but these can be easily undone. No data is deleted, financial transactions occur, or arbitrary code executed.
From the tool's definition Tool description explicitly states 'Create a new meal plan entry' with arguments for date, recipe_id, title, and entry_type. Returns 'the created mealplan entry', indicating data creation.
Documented attack patterns abuse exactly the kind of access create_mealplan 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 create_mealplan:
{
"version": "1",
"default": "deny",
"tools": {
"create_mealplan": {
"limits": [
{
"counter": "create_mealplan_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_mealplan 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.
Create a new meal plan entry. Args: date: Date for the mealplan in ISO format (YYYY-MM-DD) recipe_id: UUID of the recipe to add to the mealplan (optional) title: Title for the mealplan entry if not using a recipe (optional) entry_type: Type of mealplan entry (breakfast, lunch, dinner, side) Returns: Dict[str, Any]: JSON response containing the created mealplan entry. 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 create_mealplan: 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.
create_mealplan 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 create_mealplan 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 create_mealplan. 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.
create_mealplan 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.