Low Risk

get_tag_by_slug

get_tag_by_slug

How to control get_tag_by_slug ↓

AI agents call get_tag_by_slug to retrieve information from Mealie MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves tag data from the Mealie recipe database without modifying any state. It is a simple lookup operation with no side effects. The blast radius of misuse is minimal—an attacker could only enumerate or discover tags, not alter recipe data or cause destructive changes. No financial impact, no data destruction, no code execution involved.

From the tool's definition Tool name 'get_tag_by_slug' indicates a retrieval operation that fetches a tag by its slug identifier. The absence of mutation keywords (create, update, delete, remove) and the verb 'get' confirm this is a query/fetch operation.

Documented attack patterns abuse exactly the kind of access get_tag_by_slug 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 get_tag_by_slug:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tag_by_slug": {}
  }
}

get_tag_by_slug is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_tag_by_slug tool do? +

get_tag_by_slug. It is categorised as a Read tool in the Mealie MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tag_by_slug? +

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

get_tag_by_slug is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tag_by_slug? +

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

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

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