Record a cooked meal for rotation tracking. USE WHEN: logging what was cooked to avoid repeating meals in future planning. Deduplicates by date + recipe name. Returns confirmation with date, recipe, and people logged.
AI agents use log_meal to create or update resources in TilbudsTrolden — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TilbudsTrolden environment.
This tool creates/writes a new record of a cooked meal into a meal history log. It is reversible in nature (a log entry) and has no destructive, financial, or execution characteristics. Misuse has minimal blast radius — at worst it pollutes meal rotation history.
From the tool's definition Record a cooked meal for rotation tracking... Deduplicates by date + recipe name. Returns confirmation with date, recipe, and people logged.
Documented attack patterns abuse exactly the kind of access log_meal gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TilbudsTrolden, and nothing reaches the server without passing your rules. This is the rule we recommend for log_meal:
{
"version": "1",
"default": "deny",
"tools": {
"log_meal": {
"limits": [
{
"counter": "log_meal_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}log_meal 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.
Record a cooked meal for rotation tracking. USE WHEN: logging what was cooked to avoid repeating meals in future planning. Deduplicates by date + recipe name. Returns confirmation with date, recipe, and people logged. It is categorised as a Write tool in the TilbudsTrolden MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TilbudsTrolden MCP server in PolicyLayer and add a rule for log_meal: 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 TilbudsTrolden. Nothing to install.
log_meal 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 log_meal 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 log_meal. 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.
log_meal is provided by the TilbudsTrolden MCP server (olgasafonova/tilbudstrolden-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TilbudsTrolden, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 TilbudsTrolden tools catalogued and risk-classified — across an index of 43,000+ MCP servers.