Get one shared recipe record by ID.
AI agents call get_shared_recipe_record 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.
This tool retrieves a single shared recipe record using an ID parameter. The verb 'Get' combined with the read-only nature of fetching a record by identifier clearly indicates this is a Read operation. There are no side effects, no data modification, and no irreversible actions. The low severity reflects that retrieving recipe metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_shared_recipe_record' and description 'Get one shared recipe record by ID' indicate a retrieval operation with no modification or destructive capabilities.
Attacks that exploit this kind of access
Get one shared recipe record by ID. It is categorised as a Read tool in the Mealie MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for get_shared_recipe_record: 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.
get_shared_recipe_record is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_shared_recipe_record 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 get_shared_recipe_record. 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.
get_shared_recipe_record is provided by the Mealie MCP Server MCP server (nikopol666/mealie-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →