flash_status
Show which credentials and wallets are configured, and the supported chains.
This record as markdown: /tools/definitive-fi-flash-mcp/flash-status.md
What flash_status does on Flash
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.
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 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.
Attacks that exploit this kind of access
The rule that runs flash_status 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_status, this is the rule to start with:
flash_status 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_status call is checked against it from then on.
Questions about flash_status
Show which credentials and wallets are configured, and the supported chains. It is categorised as a Read tool in the Flash MCP Server, which means it retrieves data without modifying state.
Register the Flash MCP server in PolicyLayer and add a rule for flash_status: 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_status 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_status 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_status. 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_status 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