add_weigh_in_with_timestamps · Garmin MCP Server MCP

WHAT IT DOES

What add_weigh_in_with_timestamps does on Garmin MCP Server

AI agents use add_weigh_in_with_timestamps to create or update resources in Garmin MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Garmin MCP Server environment.

WHY IT NEEDS A POLICY

Why add_weigh_in_with_timestamps needs a policy

This tool creates or adds new health data records (weight entries with timestamps) to Garmin Connect, which is a reversible Write operation. It modifies user health data but does not delete or execute arbitrary commands. Severity is medium because misconfigured calls could add incorrect health data, though this is typically correctable.

From the tool's definition Tool name 'add_weigh_in_with_timestamps' indicates it creates new weight/health data entries. Sibling tools include 'add_body_composition', 'add_hydration_data', and 'delete_weigh_ins', establishing this as a data-writing operation on a health tracking…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_weigh_in_with_timestamps Rate-limited

add_weigh_in_with_timestamps 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": {
    "add_weigh_in_with_timestamps": {
      "limits": [
        {
          "counter": "add_weigh_in_with_timestamps_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 Garmin MCP Server, so you can run agents against it safely.

FAQ

Questions about add_weigh_in_with_timestamps

What does the add_weigh_in_with_timestamps tool do? +

add_weigh_in_with_timestamps. It is categorised as a Write tool in the Garmin MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_weigh_in_with_timestamps? +

Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for add_weigh_in_with_timestamps: 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 Garmin MCP Server. Nothing to install.

What risk level is add_weigh_in_with_timestamps? +

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

Can I rate-limit add_weigh_in_with_timestamps? +

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

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

add_weigh_in_with_timestamps is provided by the Garmin MCP Server MCP server (shubhaankar-sharma/garmin-mcp-railway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.