Batch multiple contract read calls into a single RPC request. Significantly reduces latency and RPC usage when querying multiple functions. Uses the Multicall3 contract deployed on all major networks. Perfect for portfolio analysis, price aggregation, and querying multiple contract states efficie...
AI agents call multicall 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.
Despite operating on blockchain networks, this tool only retrieves data through read operations. It batches contract queries but does not create, modify, delete, execute arbitrary code, or move assets. The tool is purely informational and has no side effects on blockchain state.
From the tool's definition Tool description explicitly states 'contract read calls' and 'querying multiple contract states'. The use case examples—'portfolio analysis, price aggregation'—are all read-only operations.
Documented attack patterns abuse exactly the kind of access multicall gives an agent:
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 multicall:
{
"version": "1",
"default": "deny",
"tools": {
"multicall": {}
}
} multicall 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.
Batch multiple contract read calls into a single RPC request. Significantly reduces latency and RPC usage when querying multiple functions. Uses the Multicall3 contract deployed on all major networks. Perfect for portfolio analysis, price aggregation, and querying multiple contract states efficiently. It is categorised as a Read tool in the EVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EVM MCP Server MCP server in PolicyLayer and add a rule for multicall: 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.
multicall 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 multicall 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 multicall. 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.
multicall 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.
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.