cancel_order
Cancel an open order on the DEX. The remaining unfilled amount will be
This record as markdown: /tools/arome3-tempo-mcp/cancel-order.md
What cancel_order does on Tempo
AI agents use cancel_order to commit financial operations through Tempo, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why cancel_order is rated Critical
Cancelling an open order on a DEX is a financial operation that alters an active trading position. While cancellation itself may be considered reversible in some sense (you could re-place the order), it directly affects financial instruments and trades on a blockchain, placing it firmly in the Financial category.
From the tool's definition 'Cancel an open order on the DEX' — directly modifies financial state by cancelling a DEX (decentralized exchange) trading order, affecting financial obligations and positions.
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 Tempo, 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:
Any call to cancel_order is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every cancel_order call is checked against it from then on.
Questions about cancel_order
Cancel an open order on the DEX. The remaining unfilled amount will be. It is categorised as a Financial tool in the Tempo MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Tempo 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 Tempo. Nothing to install.
cancel_order is a Financial 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 Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tempo, and thousands of servers like it.
Across the catalogue