Remove items from the cart by providing an updated list of items to keep
AI agents call remove_from_cart to permanently remove resources in Rami Levy MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes items from the shopping cart. While a shopping cart is not permanent data storage, removal of items is a destructive/irreversible action in context (items are deleted from the cart state). The blast radius is medium since it affects cart contents but not financial transactions or permanent data. It is more severe than a simple Write because the action removes/deletes rather than creates or modifies.
From the tool's definition Remove items from the cart by providing an updated list of items to keep
Documented attack patterns abuse exactly the kind of access remove_from_cart gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rami Levy MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_from_cart:
{
"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.
Free to start. No card required.
Remove items from the cart by providing an updated list of items to keep. It is categorised as a Destructive tool in the Rami Levy MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rami Levy MCP Server 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 Rami Levy MCP Server. Nothing to install.
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.
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.
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.
remove_from_cart is provided by the Rami Levy MCP Server MCP server (shilomagen/rami-levy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rami Levy 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.
4 Rami Levy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.