Wait for a transaction to be confirmed (mined). Polls the network until confirmation.
AI agents invoke wait_for_transaction to trigger actions in BNB Chain MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation (polling the blockchain network) whose outcome depends on arguments (the transaction hash/ID being monitored). While it doesn't directly move funds like Financial tools, it's part of transaction execution flow and can block or resume dependent operations.
From the tool's definition Tool performs network polling and waits for transaction confirmation (mined), which is an external operation with effects dependent on the transaction being monitored.
Documented attack patterns abuse exactly the kind of access wait_for_transaction 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 wait_for_transaction:
{
"version": "1",
"default": "deny",
"tools": {
"wait_for_transaction": {
"limits": [
{
"counter": "wait_for_transaction_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} wait_for_transaction stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Wait for a transaction to be confirmed (mined). Polls the network until confirmation. It is categorised as a Execute tool in the BNB Chain MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the BNB Chain MCP server in PolicyLayer and add a rule for wait_for_transaction: 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.
wait_for_transaction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wait_for_transaction 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 wait_for_transaction. 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.
wait_for_transaction 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.