cancel_order
Cancel a flight order and request refund if applicable
This record as markdown: /tools/nitrostack/cancel-order.md
What cancel_order does on Nitrostack
AI agents call cancel_order to permanently remove resources in Nitrostack, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_order is rated Critical
Cancelling an order is an irreversible operation that destroys or voids an existing transaction. While refunds involve financial operations, the core function here is destructive (cancelling/voiding the order), making it the most appropriate category. The blast radius is high because an AI agent could cancel legitimate customer orders, causing data loss and customer harm.
From the tool's definition Tool name is 'cancel_order' and description states 'Cancel a flight order' — this irreversibly removes an existing order from the system.
Attacks that exploit this kind of access
The rule that runs cancel_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_order, this is the rule to start with:
cancel_order is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every cancel_order call is checked against it from then on.
Questions about cancel_order
Cancel a flight order and request refund if applicable. It is categorised as a Destructive tool in the Nitrostack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nitrostack MCP server in PolicyLayer and add a rule for 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 Nitrostack. Nothing to install.
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 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 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.
cancel_order is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
Across the catalogue