List recipe timeline events with optional Mealie filters.
AI agents call list_recipe_timeline_events 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 read-only operation that queries and returns timeline events for a recipe. It has no side effects, does not modify data, and does not trigger external actions. The blast radius of misuse is minimal—an attacker could only view recipe timeline history, which is informational data without destructive or financial impact.
From the tool's definition Tool name contains 'list' and description states 'List recipe timeline events'; this retrieves timeline data without modification. No delete, update, create, or execute keywords present.
Attacks that exploit this kind of access
List recipe timeline events with optional Mealie filters. 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 list_recipe_timeline_events: 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.
list_recipe_timeline_events 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 list_recipe_timeline_events 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 list_recipe_timeline_events. 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.
list_recipe_timeline_events 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 →