Call read-only smart contract function via eth_call (FREE - no gas cost). EXECUTES: View/pure function on deployed contract DECODES: Return values using provided ABI FREE: No transaction fee, no state changes USE FOR: Reading contract state, querying balances, checking conditions.
AI agents call rpc_call_contract to retrieve information from HashPilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although this tool interacts with blockchain via RPC calls, the eth_call function is inherently read-only and cannot modify blockchain state. The 'no state changes' and 'no gas cost' language confirms it is a passive query operation. There is no risk of funds movement, data modification, or execution of arbitrary code—only data retrieval. This maps directly to the Read category.
From the tool's definition The tool description explicitly states it is a 'read-only smart contract function via eth_call' with 'no state changes' and 'no gas cost'.
Attacks that exploit this kind of access
Call read-only smart contract function via eth_call (FREE - no gas cost). EXECUTES: View/pure function on deployed contract DECODES: Return values using provided ABI FREE: No transaction fee, no state changes USE FOR: Reading contract state, querying balances, checking conditions. It is categorised as a Read tool in the HashPilot MCP Server, which means it retrieves data without modifying state.
Register the HashPilot MCP server in PolicyLayer and add a rule for rpc_call_contract: 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 HashPilot. Nothing to install.
rpc_call_contract 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 rpc_call_contract 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 rpc_call_contract. 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.
rpc_call_contract is provided by the HashPilot MCP server (justmert/hashpilot). 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 →