Send BEP-20 tokens (USDT, BUSD, or any BEP-20) to an address on BNB Chain
AI agents use bnb_transfer to commit financial operations through Agenti — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool irreversibly moves cryptocurrency on behalf of the AI agent. Even with correct arguments, it commits financial transactions that cannot be easily undone. The ability to send any BEP-20 token to arbitrary addresses creates extreme risk if the agent is manipulated into sending funds to wrong recipients or excessive amounts. This is the most severe financial operation and warrants critical severity.
From the tool's definition Tool description explicitly states 'Send BEP-20 tokens (USDT, BUSD, or any BEP-20) to an address on BNB Chain' - this directly transfers cryptocurrency/tokens, which constitutes moving money and committing financial obligations.
Documented attack patterns abuse exactly the kind of access bnb_transfer 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_transfer:
{
"version": "1",
"default": "deny",
"tools": {
"bnb_transfer": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to bnb_transfer is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Send BEP-20 tokens (USDT, BUSD, or any BEP-20) to an address on BNB Chain. It is categorised as a Financial tool in the Agenti MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Agenti MCP server in PolicyLayer and add a rule for bnb_transfer: 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_transfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bnb_transfer 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_transfer. 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_transfer 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.