cronometer_mark_day_complete · Fitness MCP: Risk & Policy

WHAT IT DOES

What cronometer_mark_day_complete does on FitnessMCP

AI agents use cronometer_mark_day_complete 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_mark_day_complete needs a policy

This tool creates or modifies data (marking a day as complete in a nutrition tracker) but the action is reversible—a day can typically be unmarked or its status changed back. It does not delete data, execute arbitrary code, or involve financial transactions. The blast radius is limited to the user's nutrition tracking state within Cronometer.

From the tool's definition Tool name 'cronometer_mark_day_complete' indicates modification of a day's status in Cronometer (a nutrition tracking service). The verb 'mark' combined with 'complete' suggests state change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cronometer_mark_day_complete Rate-limited

cronometer_mark_day_complete 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_mark_day_complete": {
      "limits": [
        {
          "counter": "cronometer_mark_day_complete_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_mark_day_complete

What does the cronometer_mark_day_complete tool do? +

cronometer_mark_day_complete. 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_mark_day_complete? +

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

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

Can I rate-limit cronometer_mark_day_complete? +

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

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

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