List all supported chains and tokens for deposits and withdrawals.
AI agents call wallet_supported_chains to retrieve information from Purple Flea Casino without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves informational data about supported blockchain networks and tokens. It is purely a data lookup with no side effects, no execution of code, no financial transactions, and no destructive actions.
From the tool's definition Tool name 'wallet_supported_chains' and description 'List all supported chains and tokens for deposits and withdrawals' indicate a read-only query operation that retrieves configuration data without modifying state or executing operations.
Attacks that exploit this kind of access
List all supported chains and tokens for deposits and withdrawals. It is categorised as a Read tool in the Purple Flea Casino MCP Server, which means it retrieves data without modifying state.
Register the Purple Flea Casino MCP server in PolicyLayer and add a rule for wallet_supported_chains: 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 Purple Flea Casino. Nothing to install.
wallet_supported_chains 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 wallet_supported_chains 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 wallet_supported_chains. 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.
wallet_supported_chains is provided by the Purple Flea Casino MCP server (purple-flea/agent-casino). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →