Critical Risk →

remove_from_cart

Remove products from Selver.ee cart by SKU. Server-side only - if a browser is open on selver.ee/cart, you must ALSO dispatch cart/removeItem via chrome-devtools-mcp to keep the browser in sync (see README).

How to control remove_from_cart ↓

What remove_from_cart does on Selver

AI agents call remove_from_cart to permanently remove resources in Selver — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why remove_from_cart needs a policy

Removing items from a cart is a destructive/irreversible action in the context of the cart state — the item is deleted from the cart and would need to be re-added manually. While not as severe as financial transactions or data deletion, it modifies the cart state in a way that cannot be automatically undone.

From the tool's definition Remove products from Selver.ee cart by SKU

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

How to control remove_from_cart

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_from_cart"
  ]
}

remove_from_cart disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Selver — 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.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about remove_from_cart

What does the remove_from_cart tool do? +

Remove products from Selver.ee cart by SKU. Server-side only - if a browser is open on selver.ee/cart, you must ALSO dispatch cart/removeItem via chrome-devtools-mcp to keep the browser in sync (see README). It is categorised as a Destructive tool in the Selver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_from_cart? +

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

What risk level is remove_from_cart? +

remove_from_cart is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_from_cart? +

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

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

remove_from_cart is provided by the Selver MCP server (martparve/selver-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Selver tool call.

Start from Selver, 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.

4 Selver 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.