Get auto-invest transaction history. Shows all past recurring purchases.
AI agents call BinanceAutoInvestGetHistoryList 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.
BinanceAutoInvestGetHistoryList retrieves historical transaction data without side effects. It queries past auto-investment records but does not create, modify, delete, or execute any operations. The action is purely informational, making it a Read category tool with low severity—misuse would only expose historical financial data, not enable unauthorized transactions or financial movements.
From the tool's definition Tool name includes 'Get' and description states 'Shows all past recurring purchases' with no mention of creating, modifying, or deleting data. This is a retrieval operation.
Documented attack patterns abuse exactly the kind of access BinanceAutoInvestGetHistoryList 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 BinanceAutoInvestGetHistoryList:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceAutoInvestGetHistoryList": {}
}
}BinanceAutoInvestGetHistoryList 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.
Get auto-invest transaction history. Shows all past recurring purchases. 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 BinanceAutoInvestGetHistoryList: 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.
BinanceAutoInvestGetHistoryList 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 BinanceAutoInvestGetHistoryList 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 BinanceAutoInvestGetHistoryList. 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.
BinanceAutoInvestGetHistoryList 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.