List recipe export jobs/files.
AI agents call list_recipe_exports 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 tool retrieves or queries existing export job/file data with no side effects. It performs a list/retrieval operation typical of Read category tools. No data is created, modified, deleted, or executed. The blast radius if misused is minimal—an agent could only learn about export history, not modify or delete records or trigger new operations.
From the tool's definition Tool name 'list_recipe_exports' and description 'List recipe export jobs/files' indicate a read-only query operation that retrieves information about previously created exports without modifying any data.
Attacks that exploit this kind of access
List recipe export jobs/files. 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_exports: 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_exports 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_exports 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_exports. 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_exports 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 →