Get transaction receipt (confirmation status, gas used, logs). Use this to check if a transaction has been confirmed.
AI agents call get_transaction_receipt 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 performs a read-only query operation (get/retrieve) on blockchain state data. It does not create, modify, execute, or delete anything. While it operates in the financial domain (blockchain transactions), it does not move money, commit financial obligations, or alter any data.
From the tool's definition Tool retrieves transaction receipt data including confirmation status, gas used, and logs. This is a pure data retrieval operation with no side effects or write capability—it only queries the state of an already-executed transaction.
Documented attack patterns abuse exactly the kind of access get_transaction_receipt 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_transaction_receipt:
{
"version": "1",
"default": "deny",
"tools": {
"get_transaction_receipt": {}
}
}get_transaction_receipt 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 transaction receipt (confirmation status, gas used, logs). Use this to check if a transaction has been confirmed. 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_transaction_receipt: 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_transaction_receipt 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_transaction_receipt 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_transaction_receipt. 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_transaction_receipt 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.