add_body_composition · Garmin MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_body_composition does on Garmin MCP Server

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.

WHY IT NEEDS A POLICY

Why add_body_composition needs a policy

This tool creates or modifies body composition health metrics (similar to 'add_weigh_in' and 'add_hydration_data'). It is reversible (data can be updated or deleted via 'delete_weigh_ins'), so it is Write rather than Destructive. Severity is medium because misuse could log false health data that influences fitness insights, but the impact is limited to one user's personal health record and the data is recoverable.

From the tool's definition Tool name 'add_body_composition' indicates creation/modification of body composition data. Sibling tools on the server include 'add_hydration_data', 'add_weigh_in', and 'delete_weigh_ins', confirming this server supports write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_body_composition Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_body_composition": {
      "limits": [
        {
          "counter": "add_body_composition_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_body_composition

What does the add_body_composition tool do? +

add_body_composition. 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_body_composition? +

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.

What risk level is add_body_composition? +

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

Can I rate-limit add_body_composition? +

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.

How do I block add_body_composition completely? +

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.

What MCP server provides add_body_composition? +

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