# flash_cancel_order

Cancel a resting order (limit/twap/trigger). Signs the cancel message with your funder wallet. Requires the funder private key for the order's chain.

Agent View of the PolicyLayer registry record for `flash_cancel_order`. HTML page: https://policylayer.com/tools/definitive-fi-flash-mcp/flash-cancel-order

## Facts

- Tool: `flash_cancel_order`
- Server: Flash (`@definitive-fi/flash-mcp`) — https://policylayer.com/tools/definitive-fi-flash-mcp.md
- Install: `npx -y @definitive-fi/flash-mcp`
- Homepage: https://www.npmjs.com/package/@definitive-fi/flash-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `chain` | string | yes | The chain the order is on (selects which wallet signs) |
| `orderId` | string | yes | The order id to cancel |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "flash_cancel_order",
    "arguments": {
      "chain": "<chain>",
      "orderId": "<orderId>"
    }
  }
}
```

## Why flash_cancel_order is rated Critical

This tool cancels orders, which is an irreversible operation that destroys/removes existing financial orders from the system. While superficially it might appear as Write (modifying state), the cancellation of a resting order cannot be undone—once cancelled, the order is gone. Combined with the Financial context (trading orders), this is Destructive.

From the tool's own definition: "Tool name: flash_cancel_order. Description states it 'Cancel[s] a resting order' and 'Signs the cancel message with your funder wallet.' Requires private key access. The tool irreversibly cancels existing financial orders."

## Use case

AI agents call flash_cancel_order to permanently remove resources in Flash, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Flash:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "flash_cancel_order"
  ]
}
```

## Other tools on Flash (7)

- `flash_submit_order` — Financial — https://policylayer.com/tools/definitive-fi-flash-mcp/flash-submit-order.md
- `flash_balances` — Read — https://policylayer.com/tools/definitive-fi-flash-mcp/flash-balances.md
- `flash_get_order` — Read — https://policylayer.com/tools/definitive-fi-flash-mcp/flash-get-order.md
- `flash_list_orders` — Read — https://policylayer.com/tools/definitive-fi-flash-mcp/flash-list-orders.md
- `flash_quote` — Read — https://policylayer.com/tools/definitive-fi-flash-mcp/flash-quote.md
- `flash_status` — Read — https://policylayer.com/tools/definitive-fi-flash-mcp/flash-status.md
- `flash_setup` — Write — https://policylayer.com/tools/definitive-fi-flash-mcp/flash-setup.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=definitive-fi-flash-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/definitive-fi-flash-mcp