Get block number closest to a given time or timestamp.
AI agents call get_block_by_time 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 retrieves historical block information based on a timestamp query. It is a read-only operation that queries blockchain state without modifying data, executing transactions, or triggering external operations. The blast radius of misuse is minimal—an agent could only retrieve block numbers, which are public blockchain data. There are no destructive, financial, or execution consequences.
From the tool's definition Tool name 'get_block_by_time' and description 'Get block number closest to a given time or timestamp' indicate a simple data retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_block_by_time 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_block_by_time:
{
"version": "1",
"default": "deny",
"tools": {
"get_block_by_time": {}
}
}get_block_by_time 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 block number closest to a given time or timestamp. 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_block_by_time: 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_block_by_time 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_block_by_time 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_block_by_time. 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_block_by_time 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.