Update profile fields such as calorie goal, protein goal, weight, goal type, or timezone.
AI agents use update_profile to create or update resources in Nutrition MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nutrition MCP environment.
This tool modifies user profile information (goals, weight, timezone) but the changes are reversible — the user can update their profile again with different values. There is no deletion, destruction, code execution, or financial impact.
From the tool's definition Tool description states it 'Update profile fields such as calorie goal, protein goal, weight, goal type, or timezone' — the verb 'update' and the modification of user profile data indicates creation or reversible modification of data.
Attacks that exploit this kind of access
Update profile fields such as calorie goal, protein goal, weight, goal type, or timezone. It is categorised as a Write tool in the Nutrition MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nutrition MCP server in PolicyLayer and add a rule for update_profile: 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 Nutrition MCP. Nothing to install.
update_profile 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 update_profile 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 update_profile. 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.
update_profile is provided by the Nutrition MCP server (ronkommoji/nutrition-mcp). 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 →