Get pending transactions for an address
How to control api_algod_get_pending_transactions_by_address ↓
AI agents call api_algod_get_pending_transactions_by_address 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 queries pending transaction data for a given address. It is a read-only operation that retrieves information from the blockchain without creating, modifying, deleting, or executing any transactions. The low severity reflects minimal risk if misused by an AI agent, as it only exposes existing transaction information.
From the tool's definition Tool name contains 'get' and description states 'Get pending transactions for an address' — purely retrieves data without modification or side effects.
Documented attack patterns abuse exactly the kind of access api_algod_get_pending_transactions_by_address 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_algod_get_pending_transactions_by_address:
{
"version": "1",
"default": "deny",
"tools": {
"api_algod_get_pending_transactions_by_address": {}
}
}api_algod_get_pending_transactions_by_address 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 pending transactions for an 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 api_algod_get_pending_transactions_by_address: 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_algod_get_pending_transactions_by_address 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_algod_get_pending_transactions_by_address 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_algod_get_pending_transactions_by_address. 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_algod_get_pending_transactions_by_address 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.