Low Risk

check_alerts

Check alle actieve prijsalerts en toon welke producten nu een goede deal zijn.

How to control check_alerts ↓

What check_alerts does on NL Supermarkt MCP Server

AI agents call check_alerts to retrieve information from NL Supermarkt MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why check_alerts needs a policy

This tool queries and retrieves information about price alerts and current product deals. It performs a read-only operation—checking status and displaying results without creating, modifying, deleting, or executing any side effects. The verb 'check' and 'toon' (show) confirm passive data retrieval only. There is no evidence of write, execute, destructive, or financial operations.

From the tool's definition Tool name 'check_alerts' and description 'Check alle actieve prijsalerts en toon welke producten nu een goede deal zijn' (Check all active price alerts and show which products are now a good deal) indicates retrieval and display of existing alert data and…

Documented attack patterns abuse exactly the kind of access check_alerts gives an agent:

How to control check_alerts

PolicyLayer is an MCP gateway — it sits between your AI agents and NL Supermarkt MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_alerts:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_alerts": {}
  }
}

check_alerts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register NL Supermarkt MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about check_alerts

What does the check_alerts tool do? +

Check alle actieve prijsalerts en toon welke producten nu een goede deal zijn. It is categorised as a Read tool in the NL Supermarkt MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_alerts? +

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

What risk level is check_alerts? +

check_alerts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_alerts? +

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

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

check_alerts is provided by the NL Supermarkt MCP Server MCP server (samvox1/nl-supermarkt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every NL Supermarkt MCP Server tool call.

Start from NL Supermarkt MCP Server, 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.

20 NL Supermarkt MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.