get_supported_dexes_by_network

get_supported_dexes_by_network

Server DEX Pools MCP kukapay/dex-pools-mcp
Category Read
Risk class Low
Parameters 00 required

What get_supported_dexes_by_network does on DEX Pools MCP

AI agents call get_supported_dexes_by_network to retrieve information from DEX Pools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_supported_dexes_by_network needs a policy

This tool queries and returns information about supported decentralized exchanges (DEXes) available on a specific blockchain network. It retrieves static or semi-static reference data with no side effects. The blast radius of misuse is minimal—an attacker gaining access could only observe available DEX options, not manipulate pools, execute trades, or move funds.

From the tool's definition Tool name 'get_supported_dexes_by_network' indicates a retrieval operation. The 'get_' prefix and sibling tools (get_new_pools, get_pool_details, get_supported_networks, get_top_pools_by_dex, get_trending_pools) all follow a read-only query pattern.

Questions about get_supported_dexes_by_network

What does the get_supported_dexes_by_network tool do? +

get_supported_dexes_by_network. It is categorised as a Read tool in the DEX Pools MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_supported_dexes_by_network? +

Register the DEX Pools MCP server in PolicyLayer and add a rule for get_supported_dexes_by_network: 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 DEX Pools MCP. Nothing to install.

What risk level is get_supported_dexes_by_network? +

get_supported_dexes_by_network is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_supported_dexes_by_network? +

Yes. Add a rate_limit block to the get_supported_dexes_by_network 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.

How do I block get_supported_dexes_by_network completely? +

Set action: deny in the PolicyLayer policy for get_supported_dexes_by_network. 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.

What MCP server provides get_supported_dexes_by_network? +

get_supported_dexes_by_network is provided by the DEX Pools MCP server (kukapay/dex-pools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.