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

Agent View of the PolicyLayer registry record for `get_supported_chains`. HTML page: https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-supported-chains

## Facts

- Tool: `get_supported_chains`
- Server: Mcp Omnifun (`0xzcov/omni-fun-mcp-server`) — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server.md
- Homepage: https://github.com/0xzcov/omni-fun-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade A, 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": "get_supported_chains",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Omnifun:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_supported_chains": {}
  }
}
```

## Other tools on Mcp Omnifun (7)

- `simulate_trade` — Execute — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/simulate-trade.md
- `get_agent` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-agent.md
- `get_bonding_curve` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-bonding-curve.md
- `get_how_to_buy` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-how-to-buy.md
- `get_token` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-token.md
- `get_trending_tokens` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/get-trending-tokens.md
- `search_tokens` — Read — https://policylayer.com/tools/0xzcov-omni-fun-mcp-server/search-tokens.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=0xzcov-omni-fun-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xzcov-omni-fun-mcp-server