Get all meal plans for the current household with pagination. Args: start_date: Start date for filtering meal plans (ISO format YYYY-MM-DD) end_date: End date for filtering meal plans (ISO format YYYY-MM-DD) page: Page number to retrieve per_page: Number of items per page Returns: Dict[str, Any]:...
AI agents call get_all_mealplans to retrieve information from Mealie MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/retrieval operation that reads meal plan data for the household with no side effects. It retrieves existing data without modifying, deleting, or executing operations. The blast radius of misuse is minimal—an agent could only retrieve meal plan information it should have access to within the household scope. No financial, destructive, or code execution risk.
From the tool's definition Tool description states 'Get all meal plans' with filtering and pagination parameters. The name 'get_all_mealplans' and verb 'Get' indicate data retrieval. Returns 'JSON response containing mealplan items' with no modification, creation, or deletion of data.
Documented attack patterns abuse exactly the kind of access get_all_mealplans 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 get_all_mealplans:
{
"version": "1",
"default": "deny",
"tools": {
"get_all_mealplans": {}
}
}get_all_mealplans is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all meal plans for the current household with pagination. Args: start_date: Start date for filtering meal plans (ISO format YYYY-MM-DD) end_date: End date for filtering meal plans (ISO format YYYY-MM-DD) page: Page number to retrieve per_page: Number of items per page Returns: Dict[str, Any]: JSON response containing mealplan items and pagination information. It is categorised as a Read tool in the Mealie MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for get_all_mealplans: 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.
get_all_mealplans is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_all_mealplans 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 get_all_mealplans. 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.
get_all_mealplans 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.