update_preferences · HelloFresh MCP Server MCP

WHAT IT DOES

What update_preferences does on HelloFresh MCP Server

AI agents use update_preferences 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.

WHY IT NEEDS A POLICY

Why update_preferences needs a policy

This tool modifies user account settings (dietary preferences, allergen settings, cuisine selections) but does not delete data or execute arbitrary code. It is reversible—preferences can be changed again.

From the tool's definition Tool description states 'Update your dietary and cuisine preferences' — the verb 'Update' indicates modification of stored account data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_preferences Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_preferences": {
      "limits": [
        {
          "counter": "update_preferences_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HelloFresh MCP Server, so you can run agents against it safely.

FAQ

Questions about update_preferences

What does the update_preferences tool do? +

Update your dietary and cuisine preferences on HelloFresh, such as vegetarian mode, allergen avoidance, and preferred cuisines. 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.

How do I enforce a policy on update_preferences? +

Register the HelloFresh MCP Server MCP server in PolicyLayer and add a rule for update_preferences: 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.

What risk level is update_preferences? +

update_preferences is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_preferences? +

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

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

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