Add body composition data Args: date: Date in YYYY-MM-DD format weight: Weight in kg percent_fat: Body fat percentage percent_hydration: Hydration percentage visceral_fat_mass: Visceral fat mass bone_mass: Bone mass muscle_mass: Muscle mass basal_met: Basal metabolic rate active_met: Active metab...
AI agents use add_body_composition 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 or modifies personal health data in the Garmin Connect system. It is reversible (data can be updated or corrected later), which places it in the Write category rather than Destructive.
From the tool's definition Tool description states 'Add body composition data' with multiple parameters for recording health metrics (weight, body fat percentage, muscle mass, etc.). The 'add_' prefix and the parameter list indicate the tool creates or modifies user health records.
Documented attack patterns abuse exactly the kind of access add_body_composition 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_body_composition:
{
"version": "1",
"default": "deny",
"tools": {
"add_body_composition": {
"limits": [
{
"counter": "add_body_composition_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_body_composition 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 body composition data Args: date: Date in YYYY-MM-DD format weight: Weight in kg percent_fat: Body fat percentage percent_hydration: Hydration percentage visceral_fat_mass: Visceral fat mass bone_mass: Bone mass muscle_mass: Muscle mass basal_met: Basal metabolic rate active_met: Active metabolic rate physique_rating: Physique rating metabolic_age: Metabolic age visceral_fat_rating: Visceral fat rating bmi: Body Mass Index. 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_body_composition: 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_body_composition 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_body_composition 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_body_composition. 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_body_composition 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.