Get recent transactions for an address on BNB Chain via BscScan API
AI agents call bnb_get_transactions to retrieve information from Agenti 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 blockchain via a public API. It performs no state changes, does not execute code or commands, does not delete data, and does not move funds. The only information exposure risk is to publicly available blockchain transaction data, which has minimal impact even if an AI agent misuses it by querying addresses excessively. Classification as Read is appropriate.
From the tool's definition Tool name contains 'get' and description states 'Get recent transactions for an address', indicating data retrieval with no side effects. Uses read-only BscScan API query.
Documented attack patterns abuse exactly the kind of access bnb_get_transactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agenti, and nothing reaches the server without passing your rules. This is the rule we recommend for bnb_get_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"bnb_get_transactions": {}
}
}bnb_get_transactions 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 an address on BNB Chain via BscScan API. It is categorised as a Read tool in the Agenti MCP Server, which means it retrieves data without modifying state.
Register the Agenti MCP server in PolicyLayer and add a rule for bnb_get_transactions: 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 Agenti. Nothing to install.
bnb_get_transactions 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 bnb_get_transactions 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 bnb_get_transactions. 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.
bnb_get_transactions is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 73 Agenti tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
73 Agenti tools catalogued and risk-classified — across an index of 42,500+ MCP servers.