Get liquidity pools containing a specific token. Great for finding where a token is traded and its liquidity.
AI agents call dex_get_token_pools 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 Read operation: it retrieves and queries blockchain data about liquidity pools without creating, modifying, executing code, deleting, or moving funds. The tool gathers information to answer questions about token trading venues and liquidity depths, which are harmless informational queries on blockchain state.
From the tool's definition The tool 'Get liquidity pools containing a specific token' performs information retrieval only. The description explicitly states it is 'Great for finding where a token is traded and its liquidity' — both query operations with no side effects, modifications,…
Documented attack patterns abuse exactly the kind of access dex_get_token_pools 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_token_pools:
{
"version": "1",
"default": "deny",
"tools": {
"dex_get_token_pools": {}
}
}dex_get_token_pools 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.
Get liquidity pools containing a specific token. Great for finding where a token is traded and its liquidity. 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_get_token_pools: 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_get_token_pools 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_get_token_pools 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_get_token_pools. 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_get_token_pools 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.