Get pools from a specific DEX on a network. First use getNetworks, then getNetworkDexes to find valid DEX IDs.
AI agents call getDexPools 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 tool only queries and returns pool information from decentralized exchanges. There are no side effects, state changes, or irreversible actions. It is purely informational, similar to a search or list operation. The blast radius of misuse is minimal—an agent could only retrieve unwanted pool data, not manipulate finances, execute arbitrary code, or modify blockchain state.
From the tool's definition The tool 'getDexPools' retrieves/queries pools from a DEX on a network. The description states 'Get pools from a specific DEX' with no mention of modifications, deletions, or execution of operations. It is a read-only data retrieval operation.
Documented attack patterns abuse exactly the kind of access getDexPools 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 getDexPools:
{
"version": "1",
"default": "deny",
"tools": {
"getDexPools": {}
}
}getDexPools 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 pools from a specific DEX on a network. First use getNetworks, then getNetworkDexes to find valid DEX IDs. 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 getDexPools: 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.
getDexPools 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 getDexPools 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 getDexPools. 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.
getDexPools 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.