Choose specific meals for an upcoming delivery week. You can select multiple recipes by their IDs.
AI agents use select_meals to create or update resources in HelloFresh MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HelloFresh MCP Server environment.
The tool creates or modifies user preferences for upcoming deliveries in a reversible manner. While it affects the user's HelloFresh account and future orders, the action is not destructive (selections can be changed), not financial (no payment processing), and not code execution.
From the tool's definition Tool description states 'Choose specific meals for an upcoming delivery week' and 'select multiple recipes by their IDs', which modifies user's meal selections for delivery.
Attacks that exploit this kind of access
Choose specific meals for an upcoming delivery week. You can select multiple recipes by their IDs. It is categorised as a Write tool in the HelloFresh MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HelloFresh MCP Server MCP server in PolicyLayer and add a rule for select_meals: 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 HelloFresh MCP Server. Nothing to install.
select_meals 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 select_meals 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 select_meals. 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.
select_meals is provided by the HelloFresh MCP Server MCP server (markswendsen-code/mcp-hellofresh). 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 →