Get detailed information about a specific pool. Requires network ID from getNetworks and a pool address.
AI agents call getPoolDetails 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 data retrieval operation with no side effects. It queries pool information and returns results, which is characteristic of Read operations. The severity is low because retrieving pool metadata poses minimal risk even if called inappropriately by an AI agent.
From the tool's definition Tool retrieves detailed information about a specific pool and requires only query parameters (network ID and pool address). The description contains no language indicating modification, deletion, execution of arbitrary code, or financial transactions.
Documented attack patterns abuse exactly the kind of access getPoolDetails 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 getPoolDetails:
{
"version": "1",
"default": "deny",
"tools": {
"getPoolDetails": {}
}
} getPoolDetails 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 detailed information about a specific pool. Requires network ID from getNetworks and a pool address. 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 getPoolDetails: 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.
getPoolDetails 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 getPoolDetails 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 getPoolDetails. 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.
getPoolDetails 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.