get_block_by_number

Get a block by its block number

SERVEREVM MCP Server SOURCEchulanpro5/evm-mcp-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/chulanpro5-evm-mcp-server/get-block-by-number.md

WHAT IT DOES

What get_block_by_number does on EVM MCP Server

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

RISK

Why get_block_by_number is rated Low

This tool performs a read-only operation retrieving immutable historical blockchain data. There is no capability to modify, delete, execute code, or transfer funds. The operation has minimal blast radius—an AI agent cannot misuse this to cause harm beyond potentially making excessive queries.

From the tool's definition Tool name 'get_block_by_number' and description 'Get a block by its block number' indicate a query operation that retrieves blockchain block data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_block_by_number safely

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

get_block_by_number Allowed

get_block_by_number 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": {
    "get_block_by_number": {}
  }
}

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

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

FAQ

Questions about get_block_by_number

What does the get_block_by_number tool do? +

Get a block by its block number. It is categorised as a Read tool in the EVM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_block_by_number? +

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

What risk level is get_block_by_number? +

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

Can I rate-limit get_block_by_number? +

Yes. Add a rate_limit block to the get_block_by_number 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 get_block_by_number completely? +

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

get_block_by_number is provided by the EVM MCP Server MCP server (chulanpro5/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EVM MCP Server, and thousands of servers like it.

This server

All 36 EVM MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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