Get recent transactions for a specific pool. Shows swaps, adds, removes. Requires network and pool address.
AI agents call getPoolTransactions 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 retrieves historical transaction data from a pool without modifying, executing, or deleting anything. It is a query operation that returns information about past swaps and liquidity events. While it operates in a financial domain (DEX pools), it performs no financial action itself—merely reading existing transaction records. This is categorically a Read operation with low severity.
From the tool's definition Tool description states 'Get recent transactions for a specific pool. Shows swaps, adds, removes.' The verb 'Get' and the read-only nature of querying transaction history with 'Requires network and pool address' as parameters indicate data retrieval with no…
Documented attack patterns abuse exactly the kind of access getPoolTransactions 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 getPoolTransactions:
{
"version": "1",
"default": "deny",
"tools": {
"getPoolTransactions": {}
}
}getPoolTransactions 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 recent transactions for a specific pool. Shows swaps, adds, removes. Requires network and 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 getPoolTransactions: 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.
getPoolTransactions 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 getPoolTransactions 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 getPoolTransactions. 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.
getPoolTransactions 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.