// SCAN REPORT

Iridium MCP Server

16 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

2 can modify or destroy data

14 read-only

16 tools total

Community server · catalogue entry verified 03/07/2026

How to control Iridium MCP Server ↓

TOOL MAP

What Iridium MCP Server exposes to your agents

Read (14) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Iridium MCP Server tools

Write · Medium update_food_entry This tool creates or modifies data reversibly (update operation), fitting the Write category. Write · Medium log_food_entry This tool writes a new food entry to the user's nutrition log.

2 of Iridium MCP Server's 16 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Iridium MCP Server

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

Rate limit write operations

{
  "log_food_entry": {
    "limits": [
      {
        "counter": "log_food_entry_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_body_measurements": {
    "limits": [
      {
        "counter": "get_body_measurements_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 Iridium MCP Server — 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 IRIDIUM →

Instant setup, no code required.

FULL CATALOGUE

All 16 Iridium MCP Server tools

WRITE 2 tools

Write log_food_entry Log a single food entry (cheeseburger, snack, meal, etc.) into the user Write update_food_entry Update a food entry you previously logged via log_food_entry — e.g. if the user says \

READ 14 tools

Read get_body_measurements Get body measurement history including weight, body fat percentage, and other measurements over time. Read get_exercise_progress Get performance history and 1RM trends for a specific exercise. Shows recent sets, weight progression, and est Read get_food_entries Get full individual food entries with name, macros, and all nutrients — Read get_nutrition_goals Get the user Read get_nutrition_log Get DAILY NUTRITION SUMMARIES over a date range — one row per day with Read get_personal_records Get personal records (PRs) across all exercises or for a specific exercise. Shows best 1RM, heaviest weight, m Read get_profile Get the user Read get_trainer_analysis Get weekly AI trainer analysis logs containing training recommendations, progress assessments, and coaching in Read get_training_summary Get aggregate training statistics including total workouts, exercise frequency, streaks, and workout patterns. Read get_training_volume Get volume adaptation records showing how training volume has been adjusted for each muscle group over time, i Read get_weekly_schedule Get the planned weekly training schedule showing which muscle groups or workout types are assigned to each day Read get_workout_detail Get full details of a specific workout including all exercises, sets, weights, reps, RPE, and block structure. Read get_workout_history Get recent workout history with optional filtering by date range or category. Returns workout summaries includ Read list_my_foods List the user

FAQ

Questions about Iridium MCP Server

How do I prevent bulk modifications through Iridium MCP Server? +

The Iridium MCP Server server has 2 write tools including log_food_entry, update_food_entry. 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 Iridium MCP Server.

How many tools does the Iridium MCP Server MCP server expose? +

16 tools across 2 categories: Read, Write. 14 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Iridium MCP Server? +

Register the Iridium MCP Server 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 Iridium MCP Server tool call.

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

ENFORCE POLICY ON IRIDIUM →

Instant setup, no code required.

16 Iridium MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.