Delete a warehouse
AI agents call vtex_delete_warehouse 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.
Deleting a warehouse is a destructive operation that cannot be undone. It removes a critical piece of e-commerce infrastructure, potentially impacting inventory management, order fulfillment, and business operations. The blast radius is significant as warehouse deletion affects the entire fulfillment chain. This falls squarely into the Destructive category as the primary consequence is irreversible removal.
From the tool's definition Tool name is 'vtex_delete_warehouse' with description 'Delete a warehouse' - the verb 'delete' indicates irreversible removal of data/infrastructure.
Attacks that exploit this kind of access
Delete a warehouse. 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_warehouse: 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_warehouse 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_warehouse 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_warehouse. 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_warehouse 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 →