Mark a wishlist item AS moved-to-cart (sets moved_to_cart_at = now()). This tool does NOT directly add the item to a Shopify cart — cart wrapping is the host AI's job via the existing update_cart MCP tool. Use this tool to record the move intent on the wishlist row; then call update_cart separate...
Part of the Curie Commerce server.
Free to start. No card required.
AI agents use curie_wishlist_move_to_cart to create or modify resources in Curie Commerce. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call curie_wishlist_move_to_cart repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Curie Commerce.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"curie_wishlist_move_to_cart": {
"limits": [
{
"counter": "curie_wishlist_move_to_cart_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Curie Commerce policy for all 29 tools.
These attack patterns abuse exactly the kind of access curie_wishlist_move_to_cart gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Mark a wishlist item AS moved-to-cart (sets moved_to_cart_at = now()). This tool does NOT directly add the item to a Shopify cart — cart wrapping is the host AI's job via the existing update_cart MCP tool. Use this tool to record the move intent on the wishlist row; then call update_cart separately with the product_id to complete the transfer. Pro-tier only (spends-money intent). Returns the marked-moved timestamp + a note instructing the host AI to follow up with update_cart.. It is categorised as a Write tool in the Curie Commerce MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Curie Commerce MCP server in PolicyLayer and add a rule for curie_wishlist_move_to_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 Curie Commerce. Nothing to install.
curie_wishlist_move_to_cart 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 curie_wishlist_move_to_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 curie_wishlist_move_to_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.
curie_wishlist_move_to_cart is provided by the Curie Commerce MCP server (https://chat.curie.app/api/mcp/global). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Curie Commerce tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.