// SCAN REPORT

Fitbit Googlehealth

29 tools. 12 can modify or destroy data without limits.

7 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

12 can modify or destroy data

17 read-only

29 tools total

Community server · catalogue entry verified 29/06/2026

How to control Fitbit Googlehealth ↓

TOOL MAP

What Fitbit Googlehealth exposes to your agents

Read (17) Write / Execute (5) Destructive / Financial (7)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Fitbit Googlehealth tools

Destructive · High delete_activity_log This tool irreversibly deletes user health data (activity/exercise logs). Destructive · Medium delete_body_fat_log This tool permanently removes health data records. Destructive · High delete_food_log This tool irreversibly deletes health records (food log entries) from the user's Fitbit account. Destructive · High delete_meal_preset This tool irreversibly deletes saved meal presets from the user's health data system.

12 of Fitbit Googlehealth's 29 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Fitbit Googlehealth

PolicyLayer is an MCP gateway — it sits between your AI agents and Fitbit Googlehealth, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_activity_log": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "log_activity": {
    "limits": [
      {
        "counter": "log_activity_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_activity_timeseries": {
    "limits": [
      {
        "counter": "get_activity_timeseries_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Fitbit Googlehealth — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FITBIT GOOGLEHEALTH →

Instant setup, no code required.

FULL CATALOGUE

All 29 Fitbit Googlehealth tools

DESTRUCTIVE 7 tools

Destructive delete_activity_log Remove a previously logged exercise by its logId (from log_activity output or from get_exercise_list[].logId). Destructive delete_body_fat_log Remove a previously logged body-fat entry by its logId (from log_body_fat output or from get_body_log.fat[].lo Destructive delete_food_log Remove a previously logged food entry by its logId (from log_food or log_meal_photo output). Use this to undo Destructive delete_meal_preset Remove a saved meal preset by name. Prior log entries are NOT affected. Destructive delete_sleep_log Remove a previously logged sleep entry by its logId (from log_sleep output or from get_sleep[].logId). Destructive delete_water_log Remove a previously logged water entry by its logId (from log_water output or from get_food_log.water.water[]. Destructive delete_weight_log Remove a previously logged weight entry by its logId (from log_weight output or from get_body_log.weight[].log

WRITE 5 tools

Write log_activity Record a workout that Fitbit did not auto-detect. Provide either Write log_body_fat Record a body-fat percentage reading (e.g. from a smart scale). Write log_sleep Record a sleep session that was not auto-detected. Duration is in milliseconds. Useful for nap logging or catc Write log_water Record water consumption in millilitres for the given date. Write log_weight Record a weight reading. BMI is computed by Fitbit if a height is on file.

READ 17 tools

Read get_activity_timeseries Daily values of one activity metric across a date range. Useful for trending steps, distance, calories. Cached Read get_body_log Logged weight and body fat entries across a date range. BMI is returned when Fitbit computed it. Cached 1h. Read get_cardio_fitness VO2 max estimate from Fitbit. Returned as a range string (e.g. Read get_daily_summary Steps, calories out, distance, heart rate zones (resting + zone minutes), active-minute bucket totals for a si Read get_exercise_list Returns recent exercise / activity log entries (runs, walks, workouts) in reverse chronological order. Read get_food_log Meals and water intake for the day: foods array, nutrition summary (calories/carbs/fat/fiber/protein/sodium/su Read get_heart_rate_intraday Time-series heart rate for a single day at the requested resolution. 1sec is only reliable during logged exerc Read get_heart_rate_range Daily resting heart rate and time-in-zone for each day in the range. Cached 1h. Read get_hrv Nightly HRV (daily RMSSD and deep-sleep RMSSD). Useful for recovery trending. Cached 1h. Read get_profile Returns the authenticated user profile: display name, dates, unit system, timezone, and averages. Cached for 1 Read get_respiratory_rate Sleep-derived breathing rate per day, broken down by sleep stage when available. Cached 1h. Read get_skin_temperature Overnight skin-temperature delta relative to the user baseline. Only available on supported devices. Cached 1h Read get_sleep Fitbit sleep logs (v1.2) for a date, including stage data (deep/light/rem/wake) when the device captured them. Read get_sleep_range Fitbit sleep logs (v1.2) across a date range. Good for week-over-week comparisons. Cached 1h. Read get_spo2 Nightly SpO2 averages (min / avg / max) across a date range. Cached 1h. Read list_devices Lists Fitbit devices tied to the user (battery level, last sync time, model). Cached for 1 hour. Read list_meal_presets Return every meal preset saved on this MCP server, sorted by most-recently-updated. Call this first when the u

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Fitbit Googlehealth

Can an AI agent delete data through the Fitbit Googlehealth MCP server? +

Yes. The Fitbit Googlehealth server exposes 7 destructive tools including delete_activity_log, delete_body_fat_log, delete_food_log. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Fitbit Googlehealth? +

The Fitbit Googlehealth server has 5 write tools including log_activity, log_body_fat, log_sleep. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Fitbit Googlehealth.

How many tools does the Fitbit Googlehealth MCP server expose? +

29 tools across 3 categories: Destructive, Execute, Read. 17 are read-only. 12 can modify, create, or delete data.

How do I enforce a policy on Fitbit Googlehealth? +

Register the Fitbit Googlehealth MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Fitbit Googlehealth tool call.

Deterministic rules across all 29 Fitbit Googlehealth tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FITBIT GOOGLEHEALTH →

Instant setup, no code required.

29 Fitbit Googlehealth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.