This record as markdown: /tools/graysoncadams-mealie-mcp/update-tag.md
What update_tag does on Mealie MCP Server
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.
Why update_tag is rated Medium
The tool updates tag metadata, which is a Write operation (modification of data). The blast radius is low because tag updates affect only metadata organization and do not impact financial systems, execute arbitrary code, or destroy data. The change is reversible via subsequent updates.
From the tool's definition Tool name is 'update_tag' and description states 'Update a tag's details' — this modifies existing data (a tag) reversibly without deletion or irreversible effects.
Attacks that exploit this kind of access
The rule that runs update_tag 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 update_tag, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mealie MCP Server, apply this rule, and every update_tag call is checked against it from then on.
Questions about update_tag
Update a tag's 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.
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.
update_tag 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 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.
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.
update_tag 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.
This server
Across the catalogue