Medium Risk

update_tag

Update a tag's details. Args: tag_id: The UUID of the tag to update name: New name for the tag Returns: Dict[str, Any]: The updated tag details

How to control update_tag ↓

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

Medium Risk

The tool creates or modifies data reversibly by updating an existing tag's name in the Mealie recipe database. This is a typical Write operation—the change can be undone by updating the tag again. There is no deletion (Destructive), code execution (Execute), financial commitment (Financial), or side effects beyond the intended database modification.

From the tool's definition Tool name is 'update_tag' and description states it updates 'a tag's details' by modifying the name field. This is a reversible modification operation.

Documented attack patterns abuse exactly the kind of access update_tag gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Mealie MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_tag:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_tag": {
      "limits": [
        {
          "counter": "update_tag_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Mealie MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the update_tag tool do? +

Update a tag's details. Args: tag_id: The UUID of the tag to update name: New name for the tag Returns: Dict[str, Any]: The updated tag details. 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 update_tag? +

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

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

Can I rate-limit update_tag? +

Yes. Add a rate_limit block to the update_tag 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 update_tag completely? +

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

update_tag is provided by the Mealie MCP Server MCP server (rldiao/mealie-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mealie MCP Server tool call.

Deterministic rules across all 44 Mealie MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

44 Mealie MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.