eth_json_rpc_call
AI agents invoke eth_json_rpc_call to trigger actions in Chain Debugger MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name suggests this tool makes arbitrary Ethereum JSON-RPC calls. JSON-RPC methods span a wide range: read-only calls (eth_call, eth_getBalance), state-changing transactions (eth_sendRawTransaction), and potentially destructive or financial operations.
From the tool's definition Tool name: eth_json_rpc_call — implies executing arbitrary JSON-RPC calls against an EVM blockchain; description is empty and uninformative.
Attacks that exploit this kind of access
eth_json_rpc_call. It is categorised as a Execute tool in the Chain Debugger MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chain Debugger MCP Server MCP server in PolicyLayer and add a rule for eth_json_rpc_call: 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 Chain Debugger MCP Server. Nothing to install.
eth_json_rpc_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the eth_json_rpc_call 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 eth_json_rpc_call. 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.
eth_json_rpc_call is provided by the Chain Debugger MCP Server MCP server (optimusopus/chain-debugger-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →