cronometer_remove_food_entry
AI agents call cronometer_remove_food_entry to permanently remove resources in FitnessMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing food entries from a nutrition log is an irreversible action that cannot be easily undone. While the blast radius is limited to a user's own nutrition data (not system-wide), deletion operations are categorized as Destructive. Severity is medium rather than high because the impact is confined to personal nutrition metadata without financial or system-critical consequences.
From the tool's definition Tool name 'cronometer_remove_food_entry' explicitly indicates deletion/removal of food entry records from Cronometer nutrition tracking service. The 'remove' verb combined with 'food_entry' demonstrates irreversible data deletion.
Attacks that exploit this kind of access
cronometer_remove_food_entry. It is categorised as a Destructive tool in the FitnessMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fitness MCP server in PolicyLayer and add a rule for cronometer_remove_food_entry: 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_remove_food_entry is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cronometer_remove_food_entry 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_remove_food_entry. 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_remove_food_entry 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 →