Execute blockchain RPC calls through Tatum
AI agents invoke gateway_execute_rpc to trigger actions in Sperax Ecosystem Crypto & DeFI 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.
This tool enables arbitrary execution of blockchain RPC methods, which can result in unauthorized transactions, fund transfers, contract interactions, or state modifications.
From the tool's definition Tool name 'gateway_execute_rpc' combined with description 'Execute blockchain RPC calls through Tatum' explicitly indicates execution of arbitrary blockchain operations.
Documented attack patterns abuse exactly the kind of access gateway_execute_rpc gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gateway_execute_rpc:
{
"version": "1",
"default": "deny",
"tools": {
"gateway_execute_rpc": {
"limits": [
{
"counter": "gateway_execute_rpc_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} gateway_execute_rpc 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.
Free to start. No card required.
Execute blockchain RPC calls through Tatum. It is categorised as a Execute tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for gateway_execute_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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
gateway_execute_rpc 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 gateway_execute_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 gateway_execute_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.
gateway_execute_rpc is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI 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.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.