get_supported_dexes
Returns the AMMs / DEX sources SwapWizard routes across per chain. Each DEX includes its display name and slug (e.g. "uniswap-v3") — use the slug as the 'project' filter in search_liquidity_pools to filter pools by protocol.
This record as markdown: /tools/defire-business-swapwizard-mcp/get-supported-dexes.md
What get_supported_dexes does on Swapwizard
AI agents call get_supported_dexes to retrieve information from Swapwizard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
chainId | integer | — | EVM chain ID to filter results. If omitted, returns protocols for all supported chains. |
Parameters from the server's own tool schema.
Why get_supported_dexes is rated Low
This tool queries metadata about supported DEXes and their slugs to inform other operations. It has no side effects, executes no transactions, modifies no data, and moves no funds. It is purely informational retrieval, placing it in the Read category with low severity.
From the tool's definition Tool description states it 'Returns the AMMs / DEX sources' — a read-only operation that retrieves and lists supported DEX information with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs get_supported_dexes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Swapwizard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_supported_dexes, this is the rule to start with:
get_supported_dexes 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 Swapwizard, apply this rule, and every get_supported_dexes call is checked against it from then on.
Questions about get_supported_dexes
Returns the AMMs / DEX sources SwapWizard routes across per chain. Each DEX includes its display name and slug (e.g. "uniswap-v3") — use the slug as the 'project' filter in search_liquidity_pools to filter pools by protocol. It is categorised as a Read tool in the Swapwizard MCP Server, which means it retrieves data without modifying state.
get_supported_dexes accepts 1 parameter: chainId. The full parameter table on this page comes from the server's own tool schema.
Register the Swapwizard MCP server in PolicyLayer and add a rule for get_supported_dexes: 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 Swapwizard. Nothing to install.
get_supported_dexes 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_dexes 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_dexes. 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_dexes is provided by the Swapwizard MCP server (@swapwizard/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Swapwizard, and thousands of servers like it.
This server
Across the catalogue