Log a weight measurement for a specific date. Args: - weight_kg: Weight in kilograms - date: Date YYYY-MM-DD (default: today) - comment: Optional note Returns: Confirmation of logged weight.
AI agents use fatsecret_update_weight 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 creates a new weight log entry for the user's health/nutrition tracking. It is Write (not Read, as it modifies state; not Execute/Destructive/Financial, as it has no external side effects and is fully reversible by creating a new entry). The blast radius is minimal—incorrect weight logging only affects the user's own nutrition tracking data and can be easily corrected by logging another entry.
From the tool's definition Tool description states 'Log a weight measurement' which creates a new weight entry. The return type 'Confirmation of logged weight' confirms data creation. This is a write operation that creates or modifies health tracking data reversibly.
Attacks that exploit this kind of access
Log a weight measurement for a specific date. Args: - weight_kg: Weight in kilograms - date: Date YYYY-MM-DD (default: today) - comment: Optional note Returns: Confirmation of logged weight. 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_update_weight: 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_update_weight 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_update_weight 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_update_weight. 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_update_weight 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 →