flash_setup
Connect a Definitive account for trading on Flash. The primary setup path is the interactive wizard the user runs in their OWN terminal — npx -y @definitive-fi/flash-mcp setup — which handles the API key, funder wallets, and RPCs; direct the user there rather than collecting credentials in chat. ...
This record as markdown: /tools/definitive-fi-flash-mcp/flash-setup.md
What flash_setup does on Flash
AI agents use flash_setup to create or update resources in Flash, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flash environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
rpc | object | — | Optional custom RPC URLs per chain, e.g. { "base": "https://…" }. Recommended — the public defaults are rate-limited. Pass an empty string to clear a chain's ov |
apiKey | string | — | Definitive Flash API key (starts with dpka_) |
organization | string | — | Your Definitive organization slug (optional). Stored for reference; the setup page uses whichever organization you're logged into, so this is no longer needed t |
Parameters from the server's own tool schema.
Why flash_setup is rated Medium
This tool creates or modifies account configuration and API credentials needed for trading. While it does not directly move funds (hence not Financial), it irreversibly establishes the authentication and RPC configuration that enables all downstream financial operations. It is Write (configuration modification) rather than Execute because it sets up persistent state rather than triggering one-time operations.
From the tool's definition Tool description states it "Connect[s] a Definitive account for trading on Flash" and "handles the API key, funder wallets, and RPCs". It accepts `apiKey` and `rpc` overrides, which modifies account configuration.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs flash_setup 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_setup, this is the rule to start with:
flash_setup stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_setup call is checked against it from then on.
Questions about flash_setup
Connect a Definitive account for trading on Flash. The primary setup path is the interactive wizard the user runs in their OWN terminal — npx -y @definitive-fi/flash-mcp setup — which handles the API key, funder wallets, and RPCs; direct the user there rather than collecting credentials in chat. Call this tool with no arguments to see what's configured and get the exact instructions to relay. It also accepts apiKey (safe in chat — it cannot move funds) and rpc overrides. Wallet private keys are NEVER accepted here and must never be pasted into the conversation. It is categorised as a Write tool in the Flash MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
flash_setup accepts 3 parameters: rpc, apiKey, organization. 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_setup: 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_setup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the flash_setup 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_setup. 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_setup 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