merge_units

A write tool on the Mealie MCP server.

SERVERMealie MCP Server SOURCEgraysoncadams/mealie-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/graysoncadams-mealie-mcp/merge-units.md

WHAT IT DOES

What merge_units does on Mealie MCP Server

AI agents use merge_units 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.

RISK

Why merge_units is rated Medium

Merging units in a recipe/cooking system implies modifying or combining existing unit entities, which is a reversible write operation. The action is not deletion (would be Destructive), code execution (would be Execute), or financial. Medium severity accounts for potential data integrity issues if units are merged incorrectly, affecting recipe measurements system-wide.

From the tool's definition Tool name 'merge_units' suggests combining or modifying unit records. Given the Mealie context (recipe/meal management system), this likely creates or modifies unit data, which constitutes a write operation. Empty description reduces confidence.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs merge_units 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 merge_units, this is the rule to start with:

merge_units Rate-limited

merge_units 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "merge_units": {
      "limits": [
        {
          "counter": "merge_units_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mealie MCP Server, apply this rule, and every merge_units call is checked against it from then on.

FAQ

Questions about merge_units

What does the merge_units tool do? +

merge_units is a write tool on the Mealie MCP Server MCP server. 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.

How do I enforce a policy on merge_units? +

Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for merge_units: 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.

What risk level is merge_units? +

merge_units is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit merge_units? +

Yes. Add a rate_limit block to the merge_units 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.

How do I block merge_units completely? +

Set action: deny in the PolicyLayer policy for merge_units. 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.

What MCP server provides merge_units? +

merge_units 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.

KEEP EXPLORING

More on Mealie MCP Server, and thousands of servers like it.

This server

All 93 Mealie MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →