Generate QR codes for payment address and/or payment URI from an existing payment. USE THIS WHEN: User wants QR in different size/style than original, User wants only address QR or only payment URI QR (not both), User created payment without QR (include_qr=false) and now needs it, User wants QR f...
AI agents use generate_payment_qr to create or update resources in BNB Chain MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BNB Chain MCP environment.
This tool creates/modifies data (QR code generation) in a reversible manner. It does not execute financial transactions, delete data, or run arbitrary code. It simply generates visual representations (QR codes) of existing payment information, which is a write operation.
From the tool's definition Tool name 'generate_payment_qr' and description indicate it generates QR codes for payment addresses/URIs. The action is creating new QR code artifacts (in different sizes/styles) from existing payment data.
Documented attack patterns abuse exactly the kind of access generate_payment_qr 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 generate_payment_qr:
{
"version": "1",
"default": "deny",
"tools": {
"generate_payment_qr": {
"limits": [
{
"counter": "generate_payment_qr_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_payment_qr stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate QR codes for payment address and/or payment URI from an existing payment. USE THIS WHEN: User wants QR in different size/style than original, User wants only address QR or only payment URI QR (not both), User created payment without QR (include_qr=false) and now needs it, User wants QR for gateway URL (for redirect payments). EXAMPLES:. It is categorised as a Write tool in the BNB Chain MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BNB Chain MCP server in PolicyLayer and add a rule for generate_payment_qr: 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.
generate_payment_qr is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_payment_qr 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 generate_payment_qr. 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.
generate_payment_qr 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.