Low Risk

get_block

Get block details by block number or hash

How to control get_block ↓

What get_block does on EVM MCP Server

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

Low Risk

Why get_block needs a policy

This tool retrieves immutable historical blockchain data (block details). It has no side effects, performs no state modifications, and poses no financial or destructive risk. The severe capabilities on this server (token transfers, contract interactions) are separate tools. Retrieval of public blockchain data is a read-only operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_block' and description 'Get block details by block number or hash' indicate a query operation that retrieves blockchain block data without modifying state or executing transactions.

Documented attack patterns abuse exactly the kind of access get_block gives an agent:

How to control get_block

PolicyLayer is an MCP gateway — it sits between your AI agents and EVM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_block:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_block": {}
  }
}

get_block is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register EVM MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_block

What does the get_block tool do? +

Get block details by block number or hash. 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? +

Register the EVM MCP Server MCP server in PolicyLayer and add a rule for get_block: 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? +

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

Can I rate-limit get_block? +

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

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

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

Enforce policy on every EVM MCP Server tool call.

Start from EVM MCP Server, 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.

25 EVM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.