cronometer_add_custom_food
AI agents use cronometer_add_custom_food to create or update resources in FitnessMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FitnessMCP environment.
The tool creates or modifies user nutrition data (custom food entry) within the Cronometer service. This is reversible (can be deleted or edited later) and represents data creation rather than destruction. While the description is empty, the clear action verb 'add' combined with sibling context provides high confidence.
From the tool's definition Tool name 'cronometer_add_custom_food' contains 'add' action, indicating creation of a new food entry in Cronometer nutrition tracking.
Attacks that exploit this kind of access
cronometer_add_custom_food. It is categorised as a Write tool in the FitnessMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fitness MCP server in PolicyLayer and add a rule for cronometer_add_custom_food: 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 FitnessMCP. Nothing to install.
cronometer_add_custom_food 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 cronometer_add_custom_food 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 cronometer_add_custom_food. 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.
cronometer_add_custom_food is provided by the Fitness MCP server (senoj100-alt/fitnessmcp). 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 →