delete_unit
Delete a specific measurement unit.
This record as markdown: /tools/graysoncadams-mealie-mcp/delete-unit.md
What delete_unit does on Mealie MCP Server
AI agents call delete_unit to permanently remove resources in Mealie MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_unit is rated Critical
This tool removes data (a measurement unit) that cannot be recovered without restoration from backups or re-entry. While the impact is scoped to a single unit definition rather than bulk recipe data, deletion is inherently destructive.
From the tool's definition Tool name 'delete_unit' and description 'Delete a specific measurement unit' explicitly perform a delete operation, which is irreversible.
Attacks that exploit this kind of access
The rule that runs delete_unit 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 delete_unit, this is the rule to start with:
delete_unit is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mealie MCP Server, apply this rule, and every delete_unit call is checked against it from then on.
Questions about delete_unit
Delete a specific measurement unit. It is categorised as a Destructive tool in the Mealie MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for delete_unit: 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.
delete_unit is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_unit 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 delete_unit. 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.
delete_unit is provided by the Mealie MCP Server MCP server (graysoncadams/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.
Across the catalogue