Get transaction information by ID
AI agents call api_indexer_lookup_transaction_by_id 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 is categorized as Read because it performs data retrieval without side effects. Severity is high rather than medium because: (1) the BNB Chain context makes this financial data that could expose sensitive user transaction patterns and amounts, (2) transaction lookups can reveal wallet holdings and activity to unauthorized parties, and (3) in a blockchain ecosystem, read access to financial transaction data…
From the tool's definition Tool retrieves transaction information by ID without modifying data. Description explicitly states 'Get transaction information', and the name indicates a lookup/query operation.
Documented attack patterns abuse exactly the kind of access api_indexer_lookup_transaction_by_id 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 api_indexer_lookup_transaction_by_id:
{
"version": "1",
"default": "deny",
"tools": {
"api_indexer_lookup_transaction_by_id": {}
}
}api_indexer_lookup_transaction_by_id 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 information by ID. 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 api_indexer_lookup_transaction_by_id: 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.
api_indexer_lookup_transaction_by_id 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 api_indexer_lookup_transaction_by_id 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 api_indexer_lookup_transaction_by_id. 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.
api_indexer_lookup_transaction_by_id 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.