Recent meal history for rotation planning. USE WHEN: checking what was cooked recently to avoid repetition, reviewing eating patterns. Returns meal entries with dates, recipe names, and who ate.
AI agents call get_meal_history to retrieve information from TilbudsTrolden without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_meal_history retrieves and queries existing meal history data to support meal rotation planning. It has no side effects: it does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an AI agent could only access historical meal information already stored in the system, posing no risk to data integrity, financial systems, or system operations.
From the tool's definition Tool description states it 'Returns meal entries with dates, recipe names, and who ate' — purely retrieving historical data with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access get_meal_history 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 get_meal_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_meal_history": {}
}
}get_meal_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Recent meal history for rotation planning. USE WHEN: checking what was cooked recently to avoid repetition, reviewing eating patterns. Returns meal entries with dates, recipe names, and who ate. It is categorised as a Read tool in the TilbudsTrolden MCP Server, which means it retrieves data without modifying state.
Register the TilbudsTrolden MCP server in PolicyLayer and add a rule for get_meal_history: 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.
get_meal_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_meal_history 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 get_meal_history. 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.
get_meal_history 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.