List abandoned carts (cart_token has items but no
AI agents use wafle_checkout_cart_recover to create or update resources in wafle MCP server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your wafle MCP server environment.
The tool name suggests recovering abandoned carts, which is a Write-level action (modifying cart/checkout state). However, the description is truncated mid-sentence, making it impossible to confirm the actual behavior. It could be a Read (listing carts) or a Write/Execute (triggering recovery flows).
From the tool's definition Tool name 'wafle_checkout_cart_recover' and partial description 'List abandoned carts (cart_token has items but no' — description is truncated and uninformative
Attacks that exploit this kind of access
List abandoned carts (cart_token has items but no. It is categorised as a Write tool in the wafle MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the wafle MCP server MCP server in PolicyLayer and add a rule for wafle_checkout_cart_recover: 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 wafle MCP server. Nothing to install.
wafle_checkout_cart_recover is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wafle_checkout_cart_recover 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 wafle_checkout_cart_recover. 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.
wafle_checkout_cart_recover is provided by the wafle MCP server MCP server (the33warehouse-tech/wafle-mcp). 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 →