import_recipe_from_url
Import a recipe from a URL.
This record as markdown: /tools/nikopol666-mealie-mcp/import-recipe-from-url.md
What import_recipe_from_url does on Mealie MCP Server
AI agents use import_recipe_from_url 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.
Why import_recipe_from_url is rated Medium
The tool creates and stores new recipe records in Mealie's database from external sources. While not destructive (data can be edited/deleted), and not as severe as execute (no arbitrary code execution), it does modify the recipe database state. The impact is reversible and the scope is limited to recipe creation, warranting a medium severity classification.
From the tool's definition Tool name 'import_recipe_from_url' combined with description 'Import a recipe from a URL' indicates fetching recipe data from an external source and storing it in the Mealie system. This is a create/write operation that adds new recipe data to the database.
Attacks that exploit this kind of access
The rule that runs import_recipe_from_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mealie MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_recipe_from_url, this is the rule to start with:
import_recipe_from_url stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mealie MCP Server, apply this rule, and every import_recipe_from_url call is checked against it from then on.
Questions about import_recipe_from_url
Import a recipe from a URL. 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_recipe_from_url: 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_recipe_from_url 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_recipe_from_url 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_recipe_from_url. 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_recipe_from_url 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.
More on Mealie MCP Server, and thousands of servers like it.
This server
Across the catalogue