# flash_list_orders

List recent orders for a funder wallet. Defaults to the configured EVM wallet if no address is given.

Agent View of the PolicyLayer registry record for `flash_list_orders`. HTML page: https://policylayer.com/tools/definitive-fi-flash-mcp/flash-list-orders

## Facts

- Tool: `flash_list_orders`
- 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: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 3
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `pageSize` | integer | no | Number of orders to return (max 200, default 50) |
| `statuses` | array | no | Filter by status, e.g. ORDER_STATUS_FILLED, ORDER_STATUS_PENDING |
| `funderAddress` | string | no | Funder wallet address (defaults to configured EVM wallet) |

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_list_orders",
    "arguments": {}
  }
}
```

## Why flash_list_orders is rated Low

This tool queries and retrieves existing order history for a wallet. It performs a read-only data retrieval operation. The context suggests it operates within a financial trading/DeFi system (flash loans), but the tool itself merely lists past orders without creating, modifying, deleting, or executing any transactions.

From the tool's own definition: "Tool name contains 'list' and description states 'List recent orders' — a retrieval operation with no side effects. Returns historical order data without modification or execution."

## Use case

AI agents call flash_list_orders to retrieve information from Flash without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "flash_list_orders": {}
  }
}
```

## Other tools on Flash (7)

- `flash_cancel_order` — Destructive — https://policylayer.com/tools/definitive-fi-flash-mcp/flash-cancel-order.md
- `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_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