Cancel an order
AI agents call vtex_cancel_order 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.
Cancelling an order destroys or invalidates the current order state and cannot be easily undone—it affects inventory, revenue records, fulfillment pipelines, and potentially triggers refunds. This is a destructive action with significant business impact. While not deletion of data itself, order cancellation is an irreversible state change equivalent to destructive operations.
From the tool's definition Tool name is 'vtex_cancel_order' with description 'Cancel an order'. Cancellation of orders is an irreversible operation that modifies transaction state permanently and may reverse payments, inventory allocations, or customer expectations.
Attacks that exploit this kind of access
Cancel an order. 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_cancel_order: 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_cancel_order 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_cancel_order 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_cancel_order. 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_cancel_order 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 →