cronometer_copy_day · Fitness MCP: Risk & Policy

WHAT IT DOES

What cronometer_copy_day does on FitnessMCP

AI agents use cronometer_copy_day 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_copy_day needs a policy

The tool likely creates a copy of one day's nutrition data to another day in Cronometer, which is a reversible write operation (the copy can be deleted or overwritten). This is not a read operation (it creates new data), not destructive (copies are reversible), not execute (no arbitrary code/commands), and not financial (no money movement).

From the tool's definition Tool name 'cronometer_copy_day' indicates data duplication/replication functionality. Sibling tools on the server include 'cronometer_add_food_entry' and 'cronometer_get_daily_nutrition', establishing a nutritional tracking context where copying a day would…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cronometer_copy_day Rate-limited

cronometer_copy_day 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_copy_day": {
      "limits": [
        {
          "counter": "cronometer_copy_day_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_copy_day

What does the cronometer_copy_day tool do? +

cronometer_copy_day. 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_copy_day? +

Register the Fitness MCP server in PolicyLayer and add a rule for cronometer_copy_day: 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_copy_day? +

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

Can I rate-limit cronometer_copy_day? +

Yes. Add a rate_limit block to the cronometer_copy_day 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_copy_day completely? +

Set action: deny in the PolicyLayer policy for cronometer_copy_day. 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_copy_day? +

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