log_food_entry · Iridium MCP Server MCP: Risk & Policy

WHAT IT DOES

What log_food_entry does on Iridium MCP Server

AI agents use log_food_entry to create or update resources in Iridium MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iridium MCP Server environment.

WHY IT NEEDS A POLICY

Why log_food_entry needs a policy

This tool writes a new food entry to the user's nutrition log. It is a create/write operation (adding data), reversible in principle (entries can typically be deleted), and has no financial or destructive implications. Misuse could result in incorrect nutrition tracking data being recorded.

From the tool's definition 'Log a single food entry' — creates a new nutrition record in the user's food log

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_food_entry Rate-limited

log_food_entry 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": {
    "log_food_entry": {
      "limits": [
        {
          "counter": "log_food_entry_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 Iridium MCP Server, so you can run agents against it safely.

FAQ

Questions about log_food_entry

What does the log_food_entry tool do? +

Log a single food entry (cheeseburger, snack, meal, etc.) into the user. It is categorised as a Write tool in the Iridium 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 log_food_entry? +

Register the Iridium MCP Server MCP server in PolicyLayer and add a rule for log_food_entry: 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 Iridium MCP Server. Nothing to install.

What risk level is log_food_entry? +

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

Can I rate-limit log_food_entry? +

Yes. Add a rate_limit block to the log_food_entry 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 log_food_entry completely? +

Set action: deny in the PolicyLayer policy for log_food_entry. 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 log_food_entry? +

log_food_entry is provided by the Iridium MCP Server MCP server (rostehea/iridium-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.