Medium Risk

add_weigh_in

Add a new weight measurement Args: weight: Weight value unit_key: Unit of weight ('kg' or 'lb')

How to control add_weigh_in ↓

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

Medium Risk

This tool creates new health data (a weight measurement) in a reversible manner. The data can be modified or deleted later. It does not execute arbitrary code, delete data permanently, move money, or cause irreversible changes. This is a straightforward Write operation with minimal blast radius—worst case being erroneous weight entries that can be corrected.

From the tool's definition Tool name is 'add_weigh_in' and description states 'Add a new weight measurement'. The function creates a new data record (weight entry) in the user's Garmin Connect profile.

Documented attack patterns abuse exactly the kind of access add_weigh_in gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_weigh_in:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_weigh_in": {
      "limits": [
        {
          "counter": "add_weigh_in_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Garmin MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the add_weigh_in tool do? +

Add a new weight measurement Args: weight: Weight value unit_key: Unit of weight ('kg' or 'lb'). 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? +

Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for add_weigh_in: 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? +

add_weigh_in 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? +

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

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

add_weigh_in is provided by the Garmin MCP Server MCP server (taxuspt/garmin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Garmin MCP Server tool call.

Deterministic rules across all 126 Garmin MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

126 Garmin MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.