getBlockNumber

A read tool on the MCP Ethers Wallet MCP server.

SERVERMCP Ethers Wallet SOURCEcrazyrabbitltc/mcp-ethers-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/crazyrabbitltc-mcp-ethers-server/getblocknumber.md

WHAT IT DOES

What getBlockNumber does on MCP Ethers Wallet

AI agents call getBlockNumber to retrieve information from MCP Ethers Wallet without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why getBlockNumber is rated Low

Getting the block number is a read-only query of public blockchain data with no side effects. The name and context (a wallet/blockchain interaction server listing methods for balance checks and contract queries) confirm this is data retrieval. Low severity because misuse poses minimal risk—an agent querying the block number cannot compromise funds, execute arbitrary code, or modify blockchain state.

From the tool's definition Tool name 'getBlockNumber' indicates retrieval of blockchain state data (current block number). No parameters or description provided suggesting write, execute, or destructive capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getBlockNumber safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Ethers Wallet, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getBlockNumber, this is the rule to start with:

getBlockNumber Allowed

getBlockNumber is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getBlockNumber": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Ethers Wallet, apply this rule, and every getBlockNumber call is checked against it from then on.

FAQ

Questions about getBlockNumber

What does the getBlockNumber tool do? +

getBlockNumber is a read tool on the MCP Ethers Wallet MCP server. It is categorised as a Read tool in the MCP Ethers Wallet MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getBlockNumber? +

Register the MCP Ethers Wallet MCP server in PolicyLayer and add a rule for getBlockNumber: 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 MCP Ethers Wallet. Nothing to install.

What risk level is getBlockNumber? +

getBlockNumber is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getBlockNumber? +

Yes. Add a rate_limit block to the getBlockNumber 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.

How do I block getBlockNumber completely? +

Set action: deny in the PolicyLayer policy for getBlockNumber. 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.

What MCP server provides getBlockNumber? +

getBlockNumber is provided by the MCP Ethers Wallet MCP server (crazyrabbitltc/mcp-ethers-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Ethers Wallet, and thousands of servers like it.

This server

All 69 MCP Ethers Wallet tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →