check_withdrawal_status

STEP 2: Check if withdrawal is ready to claim on Ethereum. Use blockNumber from bridge_to_ethereum response.

Server Sonic Blockchain MCP Server tairon-ai/sonic-mcp
Category Read
Risk class Low
Parameters 00 required

What check_withdrawal_status does on Sonic Blockchain MCP Server

AI agents call check_withdrawal_status to retrieve information from Sonic Blockchain MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_withdrawal_status needs a policy

This tool retrieves withdrawal status information from the blockchain. It is a read-only query operation that does not execute transactions, modify data, delete data, or move funds. The verb 'check' and the context of checking readiness before claiming indicates a pure information retrieval function.

From the tool's definition Tool name 'check_withdrawal_status' and description 'Check if withdrawal is ready to claim' indicate a query/status check operation with no side effects. The description explicitly states it checks/verifies a state without modifying it.

Questions about check_withdrawal_status

What does the check_withdrawal_status tool do? +

STEP 2: Check if withdrawal is ready to claim on Ethereum. Use blockNumber from bridge_to_ethereum response. It is categorised as a Read tool in the Sonic Blockchain MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_withdrawal_status? +

Register the Sonic Blockchain MCP Server MCP server in PolicyLayer and add a rule for check_withdrawal_status: 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.

What risk level is check_withdrawal_status? +

check_withdrawal_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_withdrawal_status? +

Yes. Add a rate_limit block to the check_withdrawal_status 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.

How do I block check_withdrawal_status completely? +

Set action: deny in the PolicyLayer policy for check_withdrawal_status. 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.

What MCP server provides check_withdrawal_status? +

check_withdrawal_status 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.