mealie_recipe_actions_list
AI agents call mealie_recipe_actions_list 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.
The tool appears to list recipe actions (likely historical actions or logs related to recipes). Despite the empty description, the '_list' suffix and context of a Mealie recipe management server strongly suggest this is a retrieval operation with no side effects. No data is created, modified, deleted, or executed.
From the tool's definition Tool name 'mealie_recipe_actions_list' indicates a list operation, which by naming convention and context within a recipe management system retrieves data without modification. The 'list' suffix is a standard Read operation pattern.
Attacks that exploit this kind of access
mealie_recipe_actions_list. 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 mealie_recipe_actions_list: 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.
mealie_recipe_actions_list 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 mealie_recipe_actions_list 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 mealie_recipe_actions_list. 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.
mealie_recipe_actions_list is provided by the Mealie MCP Server MCP server (mdlopresti/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 →