cronometer_add_food_entry · Fitness MCP: Risk & Policy

WHAT IT DOES

What cronometer_add_food_entry does on FitnessMCP

AI agents use cronometer_add_food_entry 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.

WHY IT NEEDS A POLICY

Why cronometer_add_food_entry needs a policy

This tool creates or modifies nutrition tracking data in Cronometer by adding a food entry to a user's log. While the description is empty (lowering confidence slightly), the name and context of sibling tools clearly indicate a reversible write operation.

From the tool's definition Tool name 'cronometer_add_food_entry' indicates creation of a new nutrition log entry. Sibling tools include 'cronometer_add_custom_food' and 'cronometer_copy_day', establishing this as part of Cronometer's data modification API.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cronometer_add_food_entry Rate-limited

cronometer_add_food_entry stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cronometer_add_food_entry": {
      "limits": [
        {
          "counter": "cronometer_add_food_entry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches FitnessMCP, so you can run agents against it safely.

FAQ

Questions about cronometer_add_food_entry

What does the cronometer_add_food_entry tool do? +

cronometer_add_food_entry. 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.

How do I enforce a policy on cronometer_add_food_entry? +

Register the Fitness MCP server in PolicyLayer and add a rule for cronometer_add_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.

What risk level is cronometer_add_food_entry? +

cronometer_add_food_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cronometer_add_food_entry? +

Yes. Add a rate_limit block to the cronometer_add_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.

How do I block cronometer_add_food_entry completely? +

Set action: deny in the PolicyLayer policy for cronometer_add_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.

What MCP server provides cronometer_add_food_entry? +

cronometer_add_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.