Add a new weight measurement with specific timestamps Args: weight: Weight value unit_key: Unit of weight ('kg' or 'lb') date_timestamp: Local timestamp in format YYYY-MM-DDThh:mm:ss gmt_timestamp: GMT timestamp in format YYYY-MM-DDThh:mm:ss
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.
This tool creates a new health data entry (weight measurement) in the user's Garmin Connect account, which is a reversible write operation. The impact is limited to adding a single data point to the user's fitness/health profile. There is no deletion, destruction, code execution, or financial component.
From the tool's definition The tool 'add_weigh_in_with_timestamps' creates a new weight measurement record in Garmin Connect. The description explicitly states 'Add a new weight measurement' which is a write operation that creates data.
Documented attack patterns abuse exactly the kind of access add_weigh_in_with_timestamps 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_with_timestamps:
{
"version": "1",
"default": "deny",
"tools": {
"add_weigh_in_with_timestamps": {
"limits": [
{
"counter": "add_weigh_in_with_timestamps_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Add a new weight measurement with specific timestamps Args: weight: Weight value unit_key: Unit of weight ('kg' or 'lb') date_timestamp: Local timestamp in format YYYY-MM-DDThh:mm:ss gmt_timestamp: GMT timestamp in format YYYY-MM-DDThh:mm:ss. 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.
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.
add_weigh_in_with_timestamps is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
add_weigh_in_with_timestamps 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.
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.