Low Risk

dex_get_networks

REQUIRED FIRST STEP: Get all supported blockchain networks for DEX data. Always call this first to see available network IDs like

How to control dex_get_networks ↓

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

Low Risk

This is a straightforward data retrieval operation that queries available network identifiers. It has no side effects, cannot modify or delete data, and cannot execute transactions or code. It is clearly a Read category tool with low severity since misuse would only result in viewing information about supported networks.

From the tool's definition Tool retrieves a list of supported blockchain networks for DEX data. The description indicates it 'Get[s] all supported blockchain networks' with no modification or execution capability mentioned.

Documented attack patterns abuse exactly the kind of access dex_get_networks gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for dex_get_networks:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "dex_get_networks": {}
  }
}

dex_get_networks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register BNB Chain MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the dex_get_networks tool do? +

REQUIRED FIRST STEP: Get all supported blockchain networks for DEX data. Always call this first to see available network IDs like. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dex_get_networks? +

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

What risk level is dex_get_networks? +

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

Can I rate-limit dex_get_networks? +

Yes. Add a rate_limit block to the dex_get_networks 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 dex_get_networks completely? +

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

dex_get_networks is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BNB Chain MCP tool call.

Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.