// SCAN REPORT

TilbudsTrolden

18 tools. 8 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 11 Jun 2026

8 can modify or destroy data

10 read-only

18 tools total

Community server · catalogue entry verified 11/06/2026

How to control TilbudsTrolden ↓

TOOL MAP

What TilbudsTrolden exposes to your agents

Read (10) Write / Execute (7) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous TilbudsTrolden tools

Destructive · Medium remove_recipe The tool deletes a recipe from the library. Write · Low add_recipe This tool creates or modifies recipe data within the meal planning system. Write · Low generate_shopping_list This tool creates or compiles new data (a shopping list artifact) based on input recipes. Write · Medium plan_and_shop This tool creates and modifies user-specific data artifacts (meal plans and shopping lists) but does not delete or destroy data (ruling out Destructive), does not execute arbitrary code or trigger external operations bey

8 of TilbudsTrolden's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control TilbudsTrolden

PolicyLayer is an MCP gateway — it sits between your AI agents and TilbudsTrolden, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "remove_recipe": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "log_meal": {
    "limits": [
      {
        "counter": "log_meal_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "deals_this_week": {
    "limits": [
      {
        "counter": "deals_this_week_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register TilbudsTrolden — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TILBUDSTROLDEN →

Free to start. No card required.

FULL CATALOGUE

All 18 TilbudsTrolden tools

DESTRUCTIVE 1 tools

Destructive remove_recipe Remove a recipe by name. USE WHEN: cleaning up the recipe library. Case-insensitive name matching. Returns con

WRITE 7 tools

Write log_meal Record a cooked meal for rotation tracking. USE WHEN: logging what was cooked to avoid repeating meals in futu Write log_spend Record grocery spending for budget tracking. USE WHEN: logging what was spent after a shopping trip. Returns c Write add_recipe Add or update a recipe for meal planning and deal scoring. USE WHEN: saving a new recipe or updating an existi Write generate_shopping_list Deal-optimized shopping list from specific recipes, grouped by store. USE WHEN: preparing to shop for chosen r Write plan_and_shop Score recipes, optimize a weekly meal plan, and generate a shopping list in one step. USE WHEN: Write update_household Set household members, dietary restrictions, preferred stores, country, servings. USE WHEN: first-time setup o Write update_pantry Add or remove pantry items (excluded from shopping lists). USE WHEN: updating stock after shopping or noting s

READ 10 tools

Read deals_this_week Show the best current deals from your preferred stores. USE WHEN: browsing what Read get_household Get household config: people, dietary restrictions, preferred stores, servings. USE WHEN: checking current set Read get_meal_history Recent meal history for rotation planning. USE WHEN: checking what was cooked recently to avoid repetition, re Read get_pantry List pantry items (excluded from shopping lists). USE WHEN: checking what Read get_recipes List saved recipes with ingredients, metadata, and search terms. USE WHEN: reviewing recipe library, checking Read get_spend_log Spending history with weekly averages and totals. USE WHEN: reviewing grocery budget, tracking spending trends Read get_store_offers List current offers from a specific store. USE WHEN: browsing what Read list_stores List grocery chains with dealer IDs for your country (DK/NO/SE/FI). USE WHEN: finding store IDs for get_store_ Read score_recipes Score all saved recipes against current deals, optionally optimize a weekly meal plan. USE WHEN: deciding what Read search_deals Search grocery deals across stores by keyword. Supports Denmark (DK), Norway (NO), Sweden (SE), and Finland (F

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about TilbudsTrolden

Can an AI agent delete data through the TilbudsTrolden MCP server? +

Yes. The TilbudsTrolden server exposes 1 destructive tools including remove_recipe. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through TilbudsTrolden? +

The TilbudsTrolden server has 7 write tools including log_meal, log_spend, add_recipe. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach TilbudsTrolden.

How many tools does the TilbudsTrolden MCP server expose? +

18 tools across 3 categories: Destructive, Read, Write. 10 are read-only. 8 can modify, create, or delete data.

How do I enforce a policy on TilbudsTrolden? +

Register the TilbudsTrolden MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every TilbudsTrolden tool call.

Deterministic rules across all 18 TilbudsTrolden tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TILBUDSTROLDEN →

Free to start. No card required.

18 TilbudsTrolden tools catalogued and risk-classified — across an index of 43,000+ MCP servers.