Returns the block number that was mined at a certain timestamp.
AI agents call block__getblocknobytime to retrieve information from Etherscan 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 straightforward read operation on the Ethereum blockchain, querying a specific block number based on a timestamp parameter. It has no side effects, does not create or modify data, does not execute code, and does not move funds. The blast radius of misuse is minimal—an AI agent could at worst query the blockchain excessively, which is rate-limited by typical API policies.
From the tool's definition Tool name 'block__getblocknobytime' and description 'Returns the block number that was mined at a certain timestamp' indicate a pure query operation that retrieves historical blockchain data without modifying state or executing arbitrary code.
Documented attack patterns abuse exactly the kind of access block__getblocknobytime gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Etherscan MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for block__getblocknobytime:
{
"version": "1",
"default": "deny",
"tools": {
"block__getblocknobytime": {}
}
} block__getblocknobytime 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.
Returns the block number that was mined at a certain timestamp. It is categorised as a Read tool in the Etherscan MCP MCP Server, which means it retrieves data without modifying state.
Register the Etherscan MCP server in PolicyLayer and add a rule for block__getblocknobytime: 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 Etherscan MCP. Nothing to install.
block__getblocknobytime 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 block__getblocknobytime 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 block__getblocknobytime. 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.
block__getblocknobytime is provided by the Etherscan MCP server (xiaok/etherscan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Etherscan MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
56 Etherscan MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.