🧹 ריקון העגלה לחלוטין
AI agents call clear_cart to permanently remove resources in Stevia Store MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing a cart removes all items irreversibly from the session/cart state. While cart contents are not permanent financial records, the action cannot be undone and all selected items are lost. This fits Destructive better than Write since it's a bulk removal operation. Severity is medium because the blast radius is limited to a single user's shopping session, not permanent data or financial harm.
From the tool's definition 'ריקון העגלה לחלוטין' translates to 'completely empty the cart' — the word 'לחלוטין' (completely/entirely) indicates a full wipe of cart contents
Attacks that exploit this kind of access
🧹 ריקון העגלה לחלוטין. It is categorised as a Destructive tool in the Stevia Store MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Stevia Store MCP Server MCP server in PolicyLayer and add a rule for clear_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 Stevia Store MCP Server. Nothing to install.
clear_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 clear_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 clear_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.
clear_cart is provided by the Stevia Store MCP Server MCP server (yairbarak22/mcpserverstevia). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →