Query the current status and details of a payment by its unique identifier. USE THIS WHEN: User wants to check if a payment was completed, or get details about a previously created payment. RESULT: Payment status (PE=Pending, CO=Completed, EX=Expired, CA=Cancelled), amounts, and confirmation info...
AI agents call get_payment_status 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 performs a simple data retrieval operation querying payment status and details from the blockchain. It returns information about payment state (Pending, Completed, Expired, Cancelled) and associated metadata. No financial transactions are initiated, no data is modified, and no code execution is triggered. The action is informational only, making it a Read category with low severity.
From the tool's definition Tool name is 'get_payment_status' and description states 'Query the current status and details of a payment' — purely a read operation that retrieves payment information without modifying, executing transactions, or causing side effects.
Documented attack patterns abuse exactly the kind of access get_payment_status 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 get_payment_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_payment_status": {}
}
}get_payment_status 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 current status and details of a payment by its unique identifier. USE THIS WHEN: User wants to check if a payment was completed, or get details about a previously created payment. RESULT: Payment status (PE=Pending, CO=Completed, EX=Expired, CA=Cancelled), amounts, and confirmation info. Status descriptions: PE (Pending): Waiting for customer to pay, CO (Completed): Payment confirmed on blockchain, EX (Expired): Payment time limit exceeded, CA (Cancelled): Payment was cancelled. EXAMPLES:. 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 get_payment_status: 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.
get_payment_status 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 get_payment_status 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 get_payment_status. 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.
get_payment_status 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.