Delete a product
AI agents call vtex_delete_product to permanently remove resources in MCP VTEX Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes product records from an e-commerce catalog. Deletion cannot be undone and results in loss of product data, pricing history, inventory associations, and customer reviews. In an e-commerce context, deleting products has severe business impact: broken storefront links, lost sales data, broken customer orders, and operational disruption.
From the tool's definition Tool name: 'vtex_delete_product' with description 'Delete a product'. The verb 'delete' indicates irreversible removal of data from the VTEX e-commerce platform.
Attacks that exploit this kind of access
Delete a product. It is categorised as a Destructive tool in the MCP VTEX Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP VTEX Server MCP server in PolicyLayer and add a rule for vtex_delete_product: 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 VTEX Server. Nothing to install.
vtex_delete_product 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 vtex_delete_product 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 vtex_delete_product. 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.
vtex_delete_product is provided by the MCP VTEX Server MCP server (leosepulveda/mcp-vtex). 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 →