STEP 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 are automatically detected.
AI agents use claim_on_ethereum 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 completes a cross-chain bridge withdrawal by claiming tokens on Ethereum, which constitutes a financial operation moving crypto assets. Misuse could result in incorrect token claims, loss of funds, or exploitation of bridge mechanics. The blast radius is critical as it directly involves financial asset transfers on a public blockchain.
From the tool's definition 'Claim withdrawn tokens on Ethereum after withdrawal is ready' — involves claiming tokens (financial assets) on the Ethereum blockchain using withdrawalId, token, and amount parameters from a bridge transaction.
Attacks that exploit this kind of access
STEP 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 are automatically detected. 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 claim_on_ethereum: 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.
claim_on_ethereum 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 claim_on_ethereum 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 claim_on_ethereum. 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.
claim_on_ethereum 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 →