Optimaliseer route langs meerdere winkels voor je boodschappenlijst.
AI agents invoke plan_winkelroute to trigger actions in NL Supermarkt MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a route optimization algorithm based on a shopping list and multiple store locations. It triggers an external computation (route planning) whose output depends on arguments. It doesn't merely read static data, nor does it write, delete, or involve financial transactions. Severity is low because misuse has minimal blast radius — at worst it produces a suboptimal or incorrect route.
From the tool's definition Optimaliseer route langs meerdere winkels voor je boodschappenlijst — 'optimaliseer route' implies computing/executing a routing algorithm across multiple stores
Documented attack patterns abuse exactly the kind of access plan_winkelroute gives an agent:
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 plan_winkelroute:
{
"version": "1",
"default": "deny",
"tools": {
"plan_winkelroute": {
"limits": [
{
"counter": "plan_winkelroute_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}plan_winkelroute stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Optimaliseer route langs meerdere winkels voor je boodschappenlijst. It is categorised as a Execute tool in the NL Supermarkt MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the NL Supermarkt MCP Server MCP server in PolicyLayer and add a rule for plan_winkelroute: 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.
plan_winkelroute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the plan_winkelroute 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 plan_winkelroute. 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.
plan_winkelroute 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.
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.