STEP 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!
AI agents use bridge_to_sonic to commit financial operations through Sonic Blockchain MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool initiates a cross-chain token transfer involving real financial assets. Moving tokens from Ethereum to the Sonic bridge is a financial operation that commits funds and cannot easily be reversed (bridge deposits are typically irreversible once confirmed). The support for ETH, USDC, USDT, and arbitrary ERC20 tokens means potentially large sums can be moved.
From the tool's definition 'Deposit tokens from Ethereum to Sonic bridge' — moves real crypto assets (ETH, USDC, USDT, or custom ERC20) across chains, committing financial value to a cross-chain bridge transaction
Attacks that exploit this kind of access
STEP 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!. It is categorised as a Financial tool in the Sonic Blockchain MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Sonic Blockchain MCP Server MCP server in PolicyLayer and add a rule for bridge_to_sonic: 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 Sonic Blockchain MCP Server. Nothing to install.
bridge_to_sonic is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bridge_to_sonic 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 bridge_to_sonic. 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.
bridge_to_sonic is provided by the Sonic Blockchain MCP Server MCP server (tairon-ai/sonic-mcp). 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 →