Cancel a shipment and void its label. Use when a shipment has been created but not yet picked up or tendered to UPS. The tracking number becomes invalid after voiding.
AI agents call void_shipment to permanently remove resources in UPS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool destroys the validity and utility of a created shipment label, rendering the tracking number permanently invalid. This is an irreversible action that cannot be recovered once executed. While it does not delete data from a database, it permanently invalidates a business-critical artifact (the shipping label) and associated tracking infrastructure.
From the tool's definition void_shipment performs irreversible cancellation: 'Cancel a shipment and void its label' with permanent effect: 'The tracking number becomes invalid after voiding.' This cannot be undone.
Attacks that exploit this kind of access
Cancel a shipment and void its label. Use when a shipment has been created but not yet picked up or tendered to UPS. The tracking number becomes invalid after voiding. It is categorised as a Destructive tool in the UPS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the UPS MCP Server MCP server in PolicyLayer and add a rule for void_shipment: 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 UPS MCP Server. Nothing to install.
void_shipment 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 void_shipment 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 void_shipment. 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.
void_shipment is provided by the UPS MCP Server MCP server (roscoej/ups-mcp). 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 →