aevo_cancel_all_orders
AI agents call aevo_cancel_all_orders to permanently remove resources in Aevo-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling orders is an irreversible operation that destroys the state of pending trades. While the description is empty (lowering confidence slightly), the tool name combined with the server's trading platform context clearly indicates this performs a destructive bulk action.
From the tool's definition Tool name 'aevo_cancel_all_orders' indicates irreversible cancellation of multiple orders. In a trading context, cancelling all orders is a destructive action that cannot be undone—it removes pending orders from the market.
Attacks that exploit this kind of access
aevo_cancel_all_orders. It is categorised as a Destructive tool in the Aevo-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aevo- MCP server in PolicyLayer and add a rule for aevo_cancel_all_orders: 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 Aevo-MCP. Nothing to install.
aevo_cancel_all_orders 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 aevo_cancel_all_orders 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 aevo_cancel_all_orders. 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.
aevo_cancel_all_orders is provided by the Aevo- MCP server (ribbon-finance/aevo-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 →