Skip a delivery week so you won
AI agents use skip_week 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.
Skipping a delivery week modifies the HelloFresh subscription schedule. While it has real-world impact (no meal kit delivered that week), it is generally reversible by un-skipping or rescheduling. This places it in the Write category. Severity is medium because misuse could cause a missed delivery the user wanted, but it is not financially transacting or permanently destructive.
From the tool's definition 'Skip a delivery week' — modifies the delivery schedule by skipping a week, which is a reversible account change (week can likely be unskipped or rescheduled).
Attacks that exploit this kind of access
Skip a delivery week so you won. 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 skip_week: 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.
skip_week 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 skip_week 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 skip_week. 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.
skip_week 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 →