AI agents call clear_basket to permanently remove resources in Food402 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing the entire cart removes all items without the ability to recover them, making it a destructive action. While the blast radius is limited to cart contents (no financial transaction completed yet), the action is irreversible within the session context.
From the tool's definition "Clear the entire cart" — removes all items from the basket irreversibly
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access clear_basket gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Food402, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_basket:
{
"version": "1",
"default": "deny",
"hide": [
"clear_basket"
]
} clear_basket 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.
Clear the entire cart. It is categorised as a Destructive tool in the Food402 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Food402 MCP server in PolicyLayer and add a rule for clear_basket: 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 Food402. Nothing to install.
clear_basket 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_basket 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_basket. 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_basket is provided by the Food402 MCP server (rersozlu/food402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Food402, 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.
22 Food402 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.