Cancel a previously scheduled UPS pickup by confirmation number.
AI agents call cancel_pickup 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.
Cancelling a scheduled pickup is an irreversible action that removes a confirmed logistics arrangement. Once cancelled, the pickup slot is gone and the confirmation number is invalidated. This cannot be undone — a new pickup would need to be scheduled. The blast radius is high because an AI agent misusing this tool could disrupt shipment operations, delay package deliveries, and require manual rescheduling effort.
From the tool's definition Cancel a previously scheduled UPS pickup by confirmation number
Attacks that exploit this kind of access
Cancel a previously scheduled UPS pickup by confirmation number. 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 cancel_pickup: 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.
cancel_pickup 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 cancel_pickup 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 cancel_pickup. 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.
cancel_pickup 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 →