rpc
Returns native balance, tx count, contract check, block & gas price via JSON-RPC across 48 EVM chains (ETH, Base, Arbitr Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/com-gocreativeai-omnicall-agent-tools/rpc.md
What rpc does on Omnicall — Agent Tools Gateway
AI agents call rpc to retrieve information from Omnicall — Agent Tools Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
arg | string | Yes |
Parameters from the server's own tool schema.
Why rpc is rated Low
The RPC tool retrieves blockchain state information without side effects. While it operates on financial networks (crypto), it performs only queries—no transfers, trades, or financial obligations are created. The tool is informational and monitoring-oriented. Low severity because misuse causes only information disclosure, not financial harm or code execution.
From the tool's definition Tool returns native balance, tx count, contract check, block & gas price via JSON-RPC across 48 EVM chains. These are read-only queries (balance lookup, transaction history, block inspection, gas price reporting).
Attacks that exploit this kind of access
The rule that runs rpc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Omnicall — Agent Tools Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rpc, this is the rule to start with:
rpc is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Omnicall — Agent Tools Gateway, apply this rule, and every rpc call is checked against it from then on.
Questions about rpc
Returns native balance, tx count, contract check, block & gas price via JSON-RPC across 48 EVM chains (ETH, Base, Arbitr Cost: $0.005–$0.05 USDC on Base per call. It is categorised as a Read tool in the Omnicall — Agent Tools Gateway MCP Server, which means it retrieves data without modifying state.
rpc accepts 1 parameter: arg. Required: arg. The full parameter table on this page comes from the server's own tool schema.
Register the Omnicall — Agent Tools Gateway MCP server in PolicyLayer and add a rule for rpc: 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 Omnicall — Agent Tools Gateway. Nothing to install.
rpc 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 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. 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 is provided by the Omnicall — Agent Tools Gateway MCP server (https://omnicall.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Omnicall — Agent Tools Gateway, and thousands of servers like it.
This server
Across the catalogue