get_supported_chains
Get the list of supported chains for cross-chain trading on Omni.fun. Buys use deBridge DLN (filler-based, instant). Sells use Across or deBridge sell adapters.
This record as markdown: /tools/0xzcov-omni-fun-mcp-server/get-supported-chains.md
What get_supported_chains does on Mcp Omnifun
AI agents call get_supported_chains to retrieve information from Mcp Omnifun without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_supported_chains is rated Low
This is a simple read operation that queries and returns metadata about supported chains. It has no side effects, does not execute trades, modify data, or move funds. The description of underlying bridge mechanisms (deBridge DLN, Across) is contextual but does not change the nature of this specific tool, which merely lists available chains.
From the tool's definition Tool name 'get_supported_chains' and description 'Get the list of supported chains' — retrieves informational data about available blockchain networks without modifying any state or executing transactions.
Attacks that exploit this kind of access
The rule that runs get_supported_chains safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Omnifun, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_supported_chains, this is the rule to start with:
get_supported_chains 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 Mcp Omnifun, apply this rule, and every get_supported_chains call is checked against it from then on.
Questions about get_supported_chains
Get the list of supported chains for cross-chain trading on Omni.fun. Buys use deBridge DLN (filler-based, instant). Sells use Across or deBridge sell adapters. It is categorised as a Read tool in the Mcp Omnifun MCP Server, which means it retrieves data without modifying state.
Register the Mcp Omnifun MCP server in PolicyLayer and add a rule for get_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 Mcp Omnifun. Nothing to install.
get_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 get_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 get_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.
get_supported_chains is provided by the Mcp Omnifun MCP server (0xzcov/omni-fun-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Omnifun, and thousands of servers like it.
This server
Across the catalogue