Set your daily nutrition goals for calories and macros.
AI agents use set_goals to create or update resources in Food Tracker MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Food Tracker MCP Server environment.
This tool creates or updates nutrition goal settings (calories and macros) in the user's profile or preferences. It is a reversible Write operation with no irreversible consequences, no code execution, and no financial impact. The blast radius of misuse is minimal—incorrect goals could mislead nutrition tracking but are easily corrected. Low severity due to the personal, non-destructive nature of the data affected.
From the tool's definition Tool is named 'set_goals' and description states 'Set your daily nutrition goals' — a clear create/modify operation on user configuration data.
Attacks that exploit this kind of access
Set your daily nutrition goals for calories and macros. It is categorised as a Write tool in the Food Tracker MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Food Tracker MCP Server MCP server in PolicyLayer and add a rule for set_goals: 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 Food Tracker MCP Server. Nothing to install.
set_goals 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 set_goals 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 set_goals. 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.
set_goals is provided by the Food Tracker MCP Server MCP server (neonwatty/food-tracker-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 →