# flash_status

Show which credentials and wallets are configured, and the supported chains.

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

## Facts

- Tool: `flash_status`
- 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: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "flash_status",
    "arguments": {}
  }
}
```

## Why flash_status is rated Low

This is a read-only diagnostic tool that queries the current state of configured credentials, wallets, and supported chains. It has no capability to modify data, execute transactions, delete resources, or commit financial obligations. The information displayed is informational only. While the server name suggests financial operations (flash trading context), this specific tool performs only status queries.

From the tool's own definition: "Tool shows credentials/wallets configuration and supported chains - a retrieval/status operation with no side effects. The description explicitly indicates it 'Show[s]' information rather than modifying or executing operations."

## Use case

AI agents call flash_status 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_status": {}
  }
}
```

## 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_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_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