AI agents call get_blocks to retrieve information from Web3 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves blockchain block data without any side effects. It performs a passive query operation on immutable blockchain records. No data is created, modified, deleted, or financial transactions are triggered. The blast radius of misuse is minimal—an attacker could only access historical blockchain information already publicly available on-chain.
From the tool's definition Tool name 'get_blocks' and description 'Get blocks information' indicate data retrieval with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access get_blocks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web3, and nothing reaches the server without passing your rules. This is the rule we recommend for get_blocks:
{
"version": "1",
"default": "deny",
"tools": {
"get_blocks": {}
}
}get_blocks 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 blocks information. It is categorised as a Read tool in the Web3 MCP Server, which means it retrieves data without modifying state.
Register the Web3 MCP server in PolicyLayer and add a rule for get_blocks: 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 Web3. Nothing to install.
get_blocks 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_blocks 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_blocks. 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_blocks is provided by the Web3 MCP server (tumf/web3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web3, 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.
17 Web3 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.