Remove from wishlist
AI agents call products_remove_from_wishlist to permanently remove resources in MCP Dynamics 365 Commerce Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing an item from a wishlist is a deletion action. While wishlists are user-preference data and the item itself is not destroyed, the removal of the wishlist entry is not easily reversible without re-adding the item manually, making this Destructive. Severity is medium as it affects user preference data rather than critical business records.
From the tool's definition 'products_remove_from_wishlist' and description 'Remove from wishlist' — explicitly removes an item from a wishlist
Attacks that exploit this kind of access
Remove from wishlist. It is categorised as a Destructive tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for products_remove_from_wishlist: 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 MCP Dynamics 365 Commerce Server. Nothing to install.
products_remove_from_wishlist 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 products_remove_from_wishlist 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 products_remove_from_wishlist. 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.
products_remove_from_wishlist is provided by the MCP Dynamics 365 Commerce Server MCP server (jiantmo/mcp-commerce). 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 →