Search across ALL networks for tokens, pools, and DEXes by name, symbol, or address. Good starting point when you don
AI agents call dex_search 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.
This is a search/query tool that retrieves information about DEX-related entities (tokens, pools, exchanges) without modifying state, executing code, or triggering financial transactions. It is a safe data retrieval operation with minimal risk if misused, as it cannot alter data or trigger external operations.
From the tool's definition Tool description states 'Search across ALL networks for tokens, pools, and DEXes by name, symbol, or address.' The verb 'search' and the lack of any modification, deletion, or execution capability indicates a read-only operation that retrieves data without…
Documented attack patterns abuse exactly the kind of access dex_search 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_search:
{
"version": "1",
"default": "deny",
"tools": {
"dex_search": {}
}
}dex_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search across ALL networks for tokens, pools, and DEXes by name, symbol, or address. Good starting point when you don. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain MCP server in PolicyLayer and add a rule for dex_search: 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.
dex_search 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 dex_search 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 dex_search. 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.
dex_search 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.
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.