Retrieves NFT deposit history, including network, contract address, token ID, transaction ID (if available), and timestamps.
AI agents call BinanceGetNFTDepositHistory 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 read-only operation that queries and retrieves historical deposit information. It returns data (network, contract address, token ID, transaction ID, timestamps) without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could only access historical NFT deposit records, posing no direct risk to assets, operations, or financial obligations.
From the tool's definition Tool name 'BinanceGetNFTDepositHistory' and description 'Retrieves NFT deposit history' indicates a query operation that fetches historical data about NFT deposits without modifying, executing code, or causing side effects.
Documented attack patterns abuse exactly the kind of access BinanceGetNFTDepositHistory 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 BinanceGetNFTDepositHistory:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceGetNFTDepositHistory": {}
}
}BinanceGetNFTDepositHistory 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.
Retrieves NFT deposit history, including network, contract address, token ID, transaction ID (if available), and timestamps. 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 BinanceGetNFTDepositHistory: 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.
BinanceGetNFTDepositHistory 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 BinanceGetNFTDepositHistory 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 BinanceGetNFTDepositHistory. 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.
BinanceGetNFTDepositHistory 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.