Get liquidity information for a trading pair on a DEX
AI agents call get_dex_liquidity 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 queries and retrieves liquidity data for a DEX trading pair. It performs a read-only operation—fetching informational data about existing liquidity pools. There is no indication of transaction execution, financial movements, or data modification. The potential for misuse is minimal since the tool cannot execute trades, transfer funds, or modify state; it only returns market information.
From the tool's definition Tool name 'get_dex_liquidity' and description 'Get liquidity information for a trading pair on a DEX' indicate a retrieval operation with no modification or execution of trades.
Documented attack patterns abuse exactly the kind of access get_dex_liquidity 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 get_dex_liquidity:
{
"version": "1",
"default": "deny",
"tools": {
"get_dex_liquidity": {}
}
}get_dex_liquidity 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 information for a trading pair on a DEX. 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 get_dex_liquidity: 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.
get_dex_liquidity 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 get_dex_liquidity 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 get_dex_liquidity. 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.
get_dex_liquidity 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.