flash_list_orders
List recent orders for a funder wallet. Defaults to the configured EVM wallet if no address is given.
This record as markdown: /tools/definitive-fi-flash-mcp/flash-list-orders.md
What flash_list_orders does on Flash
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
pageSize | integer | — | Number of orders to return (max 200, default 50) |
statuses | array | — | Filter by status, e.g. ORDER_STATUS_FILLED, ORDER_STATUS_PENDING |
funderAddress | string | — | Funder wallet address (defaults to configured EVM wallet) |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs flash_list_orders safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Flash, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For flash_list_orders, this is the rule to start with:
flash_list_orders is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Flash, apply this rule, and every flash_list_orders call is checked against it from then on.
Questions about flash_list_orders
List recent orders for a funder wallet. Defaults to the configured EVM wallet if no address is given. It is categorised as a Read tool in the Flash MCP Server, which means it retrieves data without modifying state.
flash_list_orders accepts 3 parameters: pageSize, statuses, funderAddress. The full parameter table on this page comes from the server's own tool schema.
Register the Flash MCP server in PolicyLayer and add a rule for flash_list_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 Flash. Nothing to install.
flash_list_orders is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the flash_list_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 flash_list_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.
flash_list_orders is provided by the Flash MCP server (@definitive-fi/flash-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Flash, and thousands of servers like it.
This server
Across the catalogue