AI agents use fatsecret_copy_day 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.
This tool performs a reversible creation operation—it duplicates food diary entries from a source date to a destination date. While it modifies the user's food diary, it does not irreversibly delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or move money (Financial). The operation is reversible by deleting the copied entries.
From the tool's definition Tool description states 'Copy all food entries from one date to another', which creates new food entry records on a target date without modifying or deleting existing entries.
Attacks that exploit this kind of access
Copy all food entries from one date to another. Useful for repeating a day. 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.
Register the Fatsecret MCP server in PolicyLayer and add a rule for fatsecret_copy_day: 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.
fatsecret_copy_day 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 fatsecret_copy_day 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 fatsecret_copy_day. 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.
fatsecret_copy_day 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.
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 →