log_food · Food Tracker MCP Server MCP: Risk & Policy

WHAT IT DOES

What log_food does on Food Tracker MCP Server

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

WHY IT NEEDS A POLICY

Why log_food needs a policy

This tool writes a new food entry to local SQLite storage. It creates data reversibly (entries can be deleted with delete_entry), has no external financial or destructive implications, and the blast radius of misuse is minimal - worst case is incorrect nutrition data being logged.

From the tool's definition 'Log a food entry to your daily food diary' - creates a new record in the diary

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_food Rate-limited

log_food 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": {
      "limits": [
        {
          "counter": "log_food_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 Food Tracker MCP Server, so you can run agents against it safely.

FAQ

Questions about log_food

What does the log_food tool do? +

Log a food entry to your daily food diary. Include nutrition info from search or estimate. It is categorised as a Write tool in the Food Tracker 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? +

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

What risk level is log_food? +

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

Can I rate-limit log_food? +

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

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

log_food is provided by the Food Tracker MCP Server MCP server (neonwatty/food-tracker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.