Critical-risk tools in Sonic Blockchain MCP Server
5 of the 17 tools in Sonic Blockchain MCP Server are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
bridge_to_ethereumFinancialSTEP 1: Withdraw tokens from Sonic to Ethereum bridge. ⚠️ ONLY supports: WETH, USDC, USDT (by symbol or address). Native S and wS tokens CANNOT be bridged. Returns withdrawalId ...
-
bridge_to_sonicFinancialSTEP 1: Deposit tokens from Ethereum to Sonic bridge. Supports: ETH (auto-wrapped to WETH), USDC, USDT, or custom ERC20 address. Returns depositId and blockNumber - save these!
-
claim_on_ethereumFinancialSTEP 3: Claim withdrawn tokens on Ethereum after withdrawal is ready. Use withdrawalId, token (symbol or address), and amount from bridge_to_ethereum response. Token decimals ar...
-
claim_rewardsFinancialClaim staking rewards from a validator. If private key is not provided, uses WALLET_PRIVATE_KEY from environment.
-
transferFinancialTransfer native S token or ERC20 tokens to another address. Supports token symbols (S, wS, WETH, USDC) or token contract addresses. If private key is not provided, uses WALLET_P...
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.