AI agents use update_custom_food 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.
The tool modifies existing custom food entries (reversible update operation), placing it in the Write category. Severity is medium because misuse could corrupt personal nutritional data or tracking accuracy, but the impact is limited to the user's own health records and is reversible. Confidence is 0.85 (not higher) due to empty description, though the name and server context make the write operation clear.
From the tool's definition Tool name 'update_custom_food' indicates modification of existing food data records. Sibling tools include 'create_custom_food' and 'add_weigh_in', confirming this server manages personal health/nutrition data with write capabilities.
Documented attack patterns abuse exactly the kind of access update_custom_food gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_custom_food:
{
"version": "1",
"default": "deny",
"tools": {
"update_custom_food": {
"limits": [
{
"counter": "update_custom_food_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_custom_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.
Free to start. No card required.
update_custom_food. 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.
Register the Garmin MCP Server MCP server in PolicyLayer and add a rule for update_custom_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 Garmin MCP Server. Nothing to install.
update_custom_food is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_custom_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.
Set action: deny in the PolicyLayer policy for update_custom_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.
update_custom_food is provided by the Garmin MCP Server MCP server (taxuspt/garmin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 126 Garmin MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
126 Garmin MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.