spraay_rpc_call
Make a premium multi-chain JSON-RPC call via Alchemy (EVM) or Helius (Solana). Supports Base, Ethereum, Arbitrum, Polygon, BNB Chain, Avalanche, and Solana. Costs $0.001 USDC.
This record as markdown: /tools/io-github-plagtech-spraay-x402-mcp/spraay-rpc-call.md
What spraay_rpc_call does on Spraay X402 Mcp
AI agents invoke spraay_rpc_call to trigger actions in Spraay X402 Mcp. 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.
Why spraay_rpc_call is rated High
This tool executes arbitrary JSON-RPC calls against multiple blockchain networks. RPC calls can be read-only (eth_getBalance) or state-changing (eth_sendRawTransaction), so the most severe applicable category is Execute. There is also a minor financial component ($0.001 USDC per call), but the primary risk is that an AI agent could submit arbitrary transactions or interact with smart contracts across multiple chains.
From the tool's definition Make a premium multi-chain JSON-RPC call via Alchemy (EVM) or Helius (Solana)... Costs $0.001 USDC
Attacks that exploit this kind of access
The rule that runs spraay_rpc_call safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Spraay X402 Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spraay_rpc_call, this is the rule to start with:
spraay_rpc_call stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Spraay X402 Mcp, apply this rule, and every spraay_rpc_call call is checked against it from then on.
Questions about spraay_rpc_call
Make a premium multi-chain JSON-RPC call via Alchemy (EVM) or Helius (Solana). Supports Base, Ethereum, Arbitrum, Polygon, BNB Chain, Avalanche, and Solana. Costs $0.001 USDC. It is categorised as a Execute tool in the Spraay X402 Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Spraay X402 MCP server in PolicyLayer and add a rule for spraay_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 Spraay X402 Mcp. Nothing to install.
spraay_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 spraay_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 spraay_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.
spraay_rpc_call is provided by the Spraay X402 MCP server (spraay-x402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Spraay X402, and thousands of servers like it.
Across the catalogue