Bulk import recipes from URLs using Mealie's bulk URL importer.
AI agents use import_recipes_from_urls 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 or adds new data (recipes) to the system in a reversible manner. While bulk operations carry wider blast radius than single-item writes, importing recipes does not permanently destroy data or execute arbitrary code—imported recipes can be modified or deleted.
From the tool's definition Tool name 'import_recipes_from_urls' combined with description stating 'Bulk import recipes' indicates creation of new recipe records in the Mealie database from external sources.
Attacks that exploit this kind of access
Bulk import recipes from URLs using Mealie's bulk URL importer. 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 import_recipes_from_urls: 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.
import_recipes_from_urls 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 import_recipes_from_urls 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 import_recipes_from_urls. 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.
import_recipes_from_urls 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 →