Query the status of a Binance Pay order. Check if payment has been received.
AI agents call BinancePayQueryOrder 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 only retrieves and inspects the status of an existing Binance Pay order. It performs no financial transactions, does not create or modify orders, and has no side effects. The action is purely informational/observational, making it a Read operation with low severity risk.
From the tool's definition Tool name includes 'Query' and description states 'Query the status' and 'Check if payment has been received' — these are read-only operations that retrieve order status information without modifying or executing transactions.
Documented attack patterns abuse exactly the kind of access BinancePayQueryOrder 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 BinancePayQueryOrder:
{
"version": "1",
"default": "deny",
"tools": {
"BinancePayQueryOrder": {}
}
}BinancePayQueryOrder 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.
Query the status of a Binance Pay order. Check if payment has been received. 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 BinancePayQueryOrder: 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.
BinancePayQueryOrder 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 BinancePayQueryOrder 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 BinancePayQueryOrder. 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.
BinancePayQueryOrder 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.