Cancel an upcoming order outright (only before its amend/cancel cutoff).
AI agents call basketeer_orders_cancel to permanently remove resources in Basketeer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling an order is an irreversible action that permanently removes a committed transaction. While not as severe as Financial (no money transfer) and technically cancellable only within a cutoff window, the act of cancelling an order cannot be undone after execution—it destroys the order state. This qualifies as Destructive rather than Write (which would be reversible modifications).
From the tool's definition Tool name contains 'cancel' and description states 'Cancel an upcoming order outright', indicating irreversible deletion or cancellation of an order.
Attacks that exploit this kind of access
Cancel an upcoming order outright (only before its amend/cancel cutoff). It is categorised as a Destructive tool in the Basketeer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Basketeer MCP server in PolicyLayer and add a rule for basketeer_orders_cancel: 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 Basketeer. Nothing to install.
basketeer_orders_cancel 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 basketeer_orders_cancel 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 basketeer_orders_cancel. 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.
basketeer_orders_cancel is provided by the Basketeer MCP server (tobyandrews1985/basketeer). 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 →