fatsecret_edit_food_entry · Fatsecret MCP: Risk & Policy

WHAT IT DOES

What fatsecret_edit_food_entry does on Fatsecret

AI agents use fatsecret_edit_food_entry to create or update resources in Fatsecret — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fatsecret environment.

WHY IT NEEDS A POLICY

Why fatsecret_edit_food_entry needs a policy

This tool modifies existing data (a food diary entry) in a way that can be easily corrected or undone by editing again or deleting the entry. There is no data destruction, financial impact, or code execution involved. The blast radius is limited to a single user's food diary record, and the changes are non-destructive.

From the tool's definition Tool description states "Edit an existing food diary entry. Can change serving size, number of units, or meal type." The parameters allow modification of food_entry_name, serving_id, number_of_units, and meal type.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fatsecret_edit_food_entry Rate-limited

fatsecret_edit_food_entry 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": {
    "fatsecret_edit_food_entry": {
      "limits": [
        {
          "counter": "fatsecret_edit_food_entry_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 Fatsecret, so you can run agents against it safely.

FAQ

Questions about fatsecret_edit_food_entry

What does the fatsecret_edit_food_entry tool do? +

Edit an existing food diary entry. Can change serving size, number of units, or meal type. Args: - food_entry_id: The entry ID to edit (from get_food_entries) - food_entry_name: Updated display name (optional) - serving_id: New serving ID (optional) - number_of_units: New number of servings (optional) - meal: New meal type (optional) Returns: Updated entry with new nutrition values. It is categorised as a Write tool in the Fatsecret MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on fatsecret_edit_food_entry? +

Register the Fatsecret MCP server in PolicyLayer and add a rule for fatsecret_edit_food_entry: 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 Fatsecret. Nothing to install.

What risk level is fatsecret_edit_food_entry? +

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

Can I rate-limit fatsecret_edit_food_entry? +

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

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

fatsecret_edit_food_entry is provided by the Fatsecret MCP server (yurzs/fatsecret-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.