fatsecret_copy_saved_meal_to_diary

Copy all foods from a saved meal template into the food diary for a specific date and meal. Args: - saved_meal_id: ID of the saved meal to copy - meal: Target meal type - date: Target date YYYY-MM-DD (default: today) Returns: Confirmation that entries were created.

Server Fatsecret yurzs/fatsecret-mcp-server
Category Write
Risk class Medium
Parameters 00 required

What fatsecret_copy_saved_meal_to_diary does on Fatsecret

AI agents use fatsecret_copy_saved_meal_to_diary 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 fatsecret_copy_saved_meal_to_diary needs a policy

This tool creates new diary entries by copying from a template—a Write operation that modifies the user's food diary reversibly. While it affects user data, it does not execute arbitrary code, delete data, move money, or have severe blast radius. A misused agent could create unwanted diary entries but these can be easily deleted via fatsecret_delete_food_entry, making this low severity.

From the tool's definition Tool description states it will 'Copy all foods from a saved meal template into the food diary', which creates new food diary entries.

Questions about fatsecret_copy_saved_meal_to_diary

What does the fatsecret_copy_saved_meal_to_diary tool do? +

Copy all foods from a saved meal template into the food diary for a specific date and meal. Args: - saved_meal_id: ID of the saved meal to copy - meal: Target meal type - date: Target date YYYY-MM-DD (default: today) Returns: Confirmation that entries were created. 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_copy_saved_meal_to_diary? +

Register the Fatsecret MCP server in PolicyLayer and add a rule for fatsecret_copy_saved_meal_to_diary: 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_copy_saved_meal_to_diary? +

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

Can I rate-limit fatsecret_copy_saved_meal_to_diary? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.